4-Core i3-9350KF 2% more perf than 18-Core i9-9980XE according to UserBenchmark
cpu.userbenchmark.com
cpu.userbenchmark.com
The 2% here is heavily weighted on single-core performance and the results are IMHO what one would expect from these two parts (the moment more than four cores are in a test, the i9 wins by a mile).
Also, the Reddit link posted seems to be all about a whole different side of the discussion (the calculation changes at userbenchmark, AMD/Intel favoring, etc).
Also, I don't understand the uproar over one small little overall percentage number- the rest of the numbers are there for anyone to easily weigh one against the other. Just a few lines down it's clear than the 18-core part demolishes the 4-core part in multi-core workloads (as anyone would expect without even visiting the website in the first place).
Being able to handle more programs at a time/etc really has no bearing on "effective speed"- if their workloads are not apps that take advantage of 18 cores (encoders, etc), it's possible a 4-core part could "feel" just as fast, or faster, than an 18-core part if it does their workload faster.
That said, the whole AMD/Intel war is less important to me because fanboyism in any amount is toxic and worth avoiding. People biased heavily enough towards one company will always see anything like this as some kind of conspiracy or attack, regardless of whether or not it's true (something I don't know in this case)
Again, I don't know if that is true. I'd love to see stats on that. My gut tells me improved single-threaded perf will always be welcome in most software because most data transforms are not not easily parallelizable. Certainly for me, more single threaded perf is always welcome in all the software I use daily.. from office suites to compilers to IDEs to photoshop to soft-PLCs/SCADA/HMI or even when opening a super large excel file with crazy forumlas. I don't think its just gaming.
The specifications of budget/cheap computers are not really an indicator of what will or wont benefit from single-threaded perf. Whether the benefit is worth paying for will obviously depend on other factors. For me its a nobrainer.
Photo/video editing on the other hand will DEFINITELY see a benefit, something I agree with- but I doubt nearly as many people do this as one would think- and again, it's clear from userbenchmark's page of data that the 18-core part in these workloads would demolish the 4-core part...so I don't see a problem.
I guess everyone just can't let go of what the "effective overall speed" number/percentage means. Maybe it's better not to have an "overall number" in the first place, since it can never always be true and is too dependent on the user? I have a feeling the majority of people reading the site are going to look at more detail than a single number anyway. They're certainly more likely to be gamers and/or enthusiasts
If single-core is all that's important, why are AMD and Intel coming out with multi-core chips at all and why are people buying them if they don't see any improvement?
My thought pattern through all of this (and maybe I'm completely off base) is that, for instance, having a 4-core part with high single-core performance might be preferable to a gamer/enthusiast (depending on common workloads) than an 18-core part with less single-core performance, and that maybe this is all a reason to consider why the weighting of UserBenchmark's "overall" score changed instead of immediately attaching the change to some anti-AMD bias
Maybe my idea that the most common workloads of UserBenchmark users (I don't claim to know their demographics, but I figured one could make assumptions based on the types of individuals that would look up benchmarks in the first place- very common among gamers) would see diminishing returns after, say 4 cores, is wrong- but that was how my thought process was going.
And a related point I'll concede (I admit my thinking maybe is just too old-school, biased, too filtered through my own experience and needs updating) is maybe there are more games and programs than I thought that actually take advantage of more than four cores.
So you would connect several PCs, notebooks to a switch, or by wifi, then you run a desktop, gnome or something, but there's a layer, heck it can be even a wrapper before running the binary.
The layer or the wrapper would just check how's going your load, memory and would the app from whatever machine has enough free resources available, the it would show you a window with you app running there (in a PC/notebook different from you "main" one), as fast as the network connection you're using to cluster up your assembled PCs / notebooks.
I think Xwindow and some go code could do the trick? There's some experience sharing clipboards/mouse/keyboard input (synergy).
What would be really necessary is a scheduler ala kubernetes (but a somewhat clever bash script could the job as well), to be able to orderly tap the free resources in several connected PCs/notebooks.
No need to rewrite thousands of apps, or design a new desktop environment completely from scratch, and you could actually would be able to run Chrome in its own hardware, just to use a hundred of tabs if you feel like to do it
https://en.m.wikipedia.org/wiki/Plan_9_from_Bell_Labs
Everything on the network was just a mount, file system, sound, cpu, etc.
Also see discussion on reddit: https://www.reddit.com/r/hardware/comments/chaofa/psa_userbe...
Multi-Core weighting is now downgraded from 10% to 2%, single-core is at 40% and quad-core at 58%: https://cpu.userbenchmark.com/Faq/What-is-the-effective-CPU-...
Counting 58% for four cores yet only 2% for >4 cores in effective speed is nothing short of an outright lie. And this change coming 2 weeks after benchmark results that put Ryzen ahead in multi-core and value proposition.
Browsers are both multiprocess and multithreaded. The ability to run a few webapps without having your system drag to a halt is a feature that's important to essentially everyone.
Webapps such as? I have a 4 core CPU from 2014 (i7-4790K) and I can't recall that ever happening to me. Primarily because any modern OS will throttle crazy runaway threads to ensure UI responsiveness, so the system doesn't 'drag to a halt' as you claim.
Also honestly.. how many people are looking at CPU benchmarks to run browsers better? I'd wager a twenty that its mostly gaming nerds who are obsessed with CPU benchmarks. Then.. its also a question of knowing your audience. I'm sure they have a better idea of who their audience is than you or I.
"Primarily because any modern OS will throttle crazy runaway threads to ensure UI responsiveness" seems like you have a particular OS in mind, and I would be interested in hearing more. I do not observe that behaviour on Debian 9 (and other Linux distros), Mac OS X, and Windows 7/8. I regularly bring any of those to UI stuttering/freeze from various workloads. Webapps only really breaks the lesser ones singlehandedly though (most of my other systems are 4+ core with 32GB+ RAM).
>"Primarily because any modern OS will throttle crazy runaway threads to ensure UI responsiveness" seems like you have a particular OS in mind, and I would be interested in hearing more.
Sure. You should read up about thread scheduling and how an OS scheduler works. I don't think I can explain that in a comment, and I'd do a poor job anyway.
>I do not observe that behaviour on Debian 9 (and other Linux distros), Mac OS X, and Windows 7/8. I regularly bring any of those to UI stuttering/freeze from various workloads. Webapps only really breaks the lesser ones singlehandedly though (most of my other systems are 4+ core with 32GB+ RAM).
I don't observe that behavior. Just for fun I ran a CPU Stress test (https://silver.urih.com/) as I'm typing this comment. CPU pegged at 100%. Not feeling a thing... https://imgur.com/a/J0l9VaP
In Linux actual scenarios for stuttering/freezing are generally represented as a load average >1, and stuttering for me generally starts to happen when I get above 3 and I assure you no Linux system will work without observable stutter when you start getting into the 20+ load average range.
In earnest I have no idea why you tried to use a JavaScript based benchmark to support your point. Even after observing it the number of nonvoluntary ctxt switches barely even registered from baseline, probably from the variety of ways browsers do their own internal threading strategies. I could not see how to change that JavaScript benchmark to make it actually provide an interesting load on my system, so I'll just leave it at that.
Factoring in all the cores tho, the i9 performance is about 3x the i3 - but at about 9x the cost. ref: https://www.cpubenchmark.net/compare/Intel-i9-9980XE-vs-Inte...
On balance, the i3 looks like a solid chip if a bit pricey for an i3.