The real deal y0

  • 1 Post
  • 36 Comments
Joined 2 years ago
cake
Cake day: July 16th, 2023

help-circle




  • Cache man, its a fun thing. 32k 32 (derp, 32 not 32k) is a common cache line size. Some compilers realise that your data might be hit often and aligns it to a cache line start to make its access fast and easy. So yes, it might allocate more memory than it should need, but then its to align the data to something like a cache line.
    There is also a hardware reasons that might also be the case. I know the wii’s main processor communicates with the co processor over memory locations that should be 32k aligned because of access speed, not only because of cache. Sometimes, more is less :')

    Hell, might even be a cause of instruction speed that loading and handling 32k of data might be faster than a single byte :').

    Then there is also the minimum heap allocation size that might factor in. Though a 32k minimum memory block seems… Excessive xD











  • Except all problems of a windows system werent on win7. Bloat? Minimal, was mostly the theme that was heavy but could be disabled. Forced updates? Didnt exist yet. Hardware requirements? A running pc. Half assed new ui? Didnt exist yet. Confusing configs that were all over the place? Nope, started in win8 and 10. Software comparability? 90% hell yes.

    Win7 was a polished vista, with loads of bloat removed, performance improvements and 1000% more stable.
    Win8 started screwing with shit and moving stuff partly and it went downhill from there.

    And im also comparing it to os’ of the time. Clearly with todays tech id pick a linux over win7 anyday, but in those days win7 was king