Quote:
Originally Posted by SmartCat When we upgrade to SSD and increase RAM, will the Geekbench score of an old desktop change? That is, does Geekbench measure the performance of processor only or the entire system?
|
Good question! I've not used Geekbench much since the Geekbench 3/4 days, as it used to be only for phones, but it's a CPU benchmark and these "CPU" benchmarks SHOULD only test how many instructions per second of various types of instructions (Integer, floating point, etc.) and test these across the variety of CISC instruction sets that have been added over the years. e.g. AVX enables huge speed ups in a lot of calculations, it seems particulary in floating point calculations. So the benchmark should be programmed in a way that a machine with AVX/AVX2/AVX-512 (if applicable to the test) should take advantage of it, thus correctly rewarding the machine for it's newer instruction set and penalizing older machines.
Additionally, it should be big enough to utilize the full cache of the CPU to award higher scores to CPUs with more cache, without being so big that it depends on your memory transfer speeds as well.
However, looking into it's internals (
https://www.geekbench.com/doc/geekbe...-internals.pdf), it's clear that Geekbench has evolved a lot, and some of these productivity workloads (file compression, photo library and likely a few others) may also depend on how much RAM you have and especially on what speed/latency it's running at. This also assumes the very old machine has enough RAM to run whatever version of Windows + background RAMs comfortably without interfering with the benchmark. SSD vs HDD should not make a difference here.
A simple RAM upgrade with a mismatched set will result in the lower of the two speeds/slower timings if same speed (higher latency) being applied, and that may slow it down by a bit. Even though the system itself will likely perform much better with the extra RAM.
But I wouldn't read too much into Geekbench other than getting a ballpark estimate, anyway.
Quote:
There is a valid reason for the way Microsoft manages resources. Let's say you are running tasks in the background that are processor intensive. For example:
- Large file transfers or zipping/unzipping
- 3D Rendering or video editing
- Large set data analysis
While that is happening, you would also want to work on something else, since the above tasks take a long time.
In the above use case, Chrome OS/Chromebook will falter badly, even if you equip it with the latest hardware. That's because Chrome OS is designed to throttle background tasks in favour of "foreground" tasks. As a byproduct, you get stable performance (for normal tasks) even if the hardware is below par.
|
Correct. Most desktop-based OSes manage it that way. What I meant was that on the slower machines I've used, they follow this behavior not only for user programs but also something like OneDrive syncing in the background, Defender running an ill-timed scan or Windows Update downloading some updates which results in it slowing down to a crawl even though the machine can easily handle the bare OS, a Word document + YouTube in the background.
There is also tons of bloatware, like the Xbox Game Bar that's great if you want to record gameplay, not good on a slow machine already struggling to catch it's breath. The search bar w/ads is horrific now, takes a full 3 seconds to load up on a 6-core i7 at near idle. All these things add up to provide a bad experience for the users on a low-power machine. Some of it is part of the desktop OS experience. But all I know is, Win10 wasn't as resource intensive, and machines that ran Win8.1 perfectly fine struggled with Win10, too. My Surface Pro 2 was never slow a day in it's life while running Win8.1, and that's while doing intensive coding and testing w/ an Android emulator, but I would say it's barely able to browse the web with the latest versions of Win10. It's not overheating or anything either, just...slow. In fact even my Surface Pro 6 (8th gen i7, 16GB RAM) has been far from snappy since I installed Windows 11. This is an easy win for any competitor, and I'd happily switch those machines to Linux if I could reliably say that drivers wouldn't be an issue.
Right now, I have Firefox with 6 tabs open, using up 2.5GB according to Task Manager, Steam in the background doing nothing, and Teams and Skype. But my machine is still using 12.5GB of RAM(80%) and has 31.8GB committed (used) out of a total of 41GB of available memory (including page file). I guess a lot of this is because of SuperFetch, the cache I mentioned earlier. But at least some of it is also because of some Windows processes that I don't strictly need to be running.