Announcement

Collapse
No announcement yet.

An Introduction To Intel's Tremont Microarchitecture

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #41
    Originally posted by duby229 View Post

    Then I guess it might be surprising to you that AMDs GPUs have many times more execution units than nVidias...
    What? No they don't. The RTX 2080 Ti has 4352 CUDA cores. The Vega VII has 3840 CUs. GFlops-wise they are the same. Each CUs or CUDA cores are capable of 2 FLOPs per cycle.

    Comment


    • #42
      Originally posted by c117152 View Post
      What's up with that decoder's width?
      In typical usage, it's half that width.

      At a branch instruction, it runs both options through the decoders, and then parks the one that fails - it assumes the branch will eventually be taken, at which time it can just switch decoders and keep on running, like a relay race.

      Comment


      • #43
        Originally posted by sandy8925 View Post
        True, but multiple cores are very useful. For example, on my Nexus 6, for some idiotic reason, cores are shut down as battery charge level decreases. So when the battery reaches 75% and less, 2 cores are turned off and only 2 are available. There's a huge drop in performance and responsiveness.

        It turns out, that multiple cores able to run multiple processes/threads in parallel can significantly boost responsiveness - who knew?
        FYI: Android is not a real-time OS by any stretch of the imagination, and it usually does not even use the soft-realtime features from Linux kernel (so it won't just interrupt its processing when a high-priority input arrives), it's running 90% bloat, the CPU schedulers in the default firmware were written by hitting the keyboard with a fist multiple times without looking at the screen, and so on and so forth.

        Really you can't use that as a reason to "add moar cores".
        Last edited by starshipeleven; 10-25-2019, 09:15 AM.

        Comment


        • #44
          Originally posted by Alex/AT View Post
          Design target: single-thread performance.
          Someone tell them it's 2019 already.
          FYI: single-threaded performance is still very much a thing in 2019, especially for a weak core.

          Comment


          • #45
            Originally posted by Alex/AT View Post
            Fortunately, the typical number of different tasks running on modern general purpose CPU is more than one.
            It's 2019. DOS and likes are way in the past.
            You are confusing multithreading with multiprogramming.

            DOS is monoprogramming so it can run a SINGLE process until it has finished and releases control to the "OS".

            This hardware is most likely going to run a multiprogramming OS of some kind, where multiple processes will be allocated time so they can be run "together" without taking exclusive control of the CPU
            Last edited by starshipeleven; 10-25-2019, 09:14 AM.

            Comment


            • #46
              Originally posted by sandy8925 View Post
              Actually, it is. When you have multiple cores/processors, you're actually running things in parallel. Not just providing the appearance of running things in parallel. It does make a big difference as far as responsiveness.
              Responsiveness a matter of effective process scheduling, also note that on most multicore systems you are still running far more processes than you have cores for so there is still a BIG component of process scheduling and "appearance of running in parallel".

              Comment


              • #47
                Originally posted by uid313 View Post
                I don't know about compiling, but aren't ARM processors really good for video decoding considering all phones and tablets that are used for video decoding with very little power usage?
                No they are not. Phones and tablets have decoding acceleration hardware and offload the media decoding to that.

                Without hardware decode most ARM devices can't show more than 720p video.
                Last edited by starshipeleven; 10-25-2019, 12:07 PM.

                Comment


                • #48
                  Originally posted by starshipeleven View Post
                  Responsiveness a matter of effective process scheduling, also note that on most multicore systems you are still running far more processes than you have cores for so there is still a BIG component of process scheduling and "appearance of running in parallel".
                  In the cloud, future CPUs will surely reach 1024 x86 cores per CPU package because the workloads, such as websites hosted on a single CPU with 4-16 cores allocated per website, are highly independent. 1024/16=64. This will require higher-bandwidth memory on the motherboard and/or very large L3/L4 caches on the CPU (1-4 GiB L3/L4 cache), and higher-bandwidth network connections.

                  Usefulness of 1024 x86 cores in desktop and notebook CPUs is less probable.

                  Comment


                  • #49
                    Originally posted by c117152 View Post
                    What's up with that decoder's width?
                    Maybe there are 2 threads per core.

                    Comment


                    • #50
                      Originally posted by starshipeleven View Post
                      FYI: Android is not a real-time OS by any stretch of the imagination, and it usually does not even use the soft-realtime features from Linux kernel (so it won't just interrupt its processing when a high-priority input arrives), it's running 90% bloat, the CPU schedulers in the default firmware were written by hitting the keyboard with a fist multiple times without looking at the screen, and so on and so forth.

                      Really you can't use that as a reason to "add moar cores".
                      Realtime isn't actually useful there, except potentially for phone calls, and other types of audio and video calls. It's not some kind of nuclear reactor safety and monitoring usecase.

                      Comment

                      Working...
                      X