| |||
![]()
|
![]() ![]() |
![]()
that's all fine and good, but lots of people still do stuff on machines which are vastly underspecified in terms of ram, and believe me, they prefer occasional stutters to programs crushing with OOM errors. Especially relevant considering the number laptops that have 8 gb by default in the lowest spec, and even the mid spec (sold till this day), of which empty OS eats 2-4 GB, so the user can open like 4 heavy websites and begin swapping after that. Several years ago browsers learned how to unload tabs from memory, but same can't be said about desktop apps. The alleged "25% performance penalty" is probably bullshit for today's cpus and today's memory, where most of the costs happen on cache misses anyway, and was only relevant for the earliest 386 era machines, especially considering the need for modern concurrency and the multi-levelness caches. I suspect that on modern cpus the paging stuff is almost free with translation lookaside buffer having the appropriate entries. With Java and C# you get 100% performance penalty and memory bloat penalty so that's not really an option either. Добавить комментарий: |
|||
![]() |
![]() |