-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ryzen 3600 test #1
Comments
Saw this and figured I would add mine. 3950x Results: |
Why not? Ryzen 9 3900 (not X: it's the slower version). |
Jumping on the statistics with a 3700x |
3900X here - using Rampagy's fork in order to run all tests (both single and multi) and save to file EDIT: hmmm I think the final score on test 7 multi threaded is wrong....... I will try it again as soon as I can EDIT2: used TheRainDoodle's original benchmark - included binary for linux... |
@wickwire Thanks for testing out my fork! Test 7 is a little curious, but based on the code it does have have a 1:1 scaling from instructions to Phenom II's. The scalings are unchanged from TheRainDoodle's original benchmark. Anyways here are my results: |
@Rampagy If you check the sources, the 1:1 is only in the Linux source, compare Windows, and I assume it's an omission. What I think is most interesting about this series of benchmarks: ten years on, you have a 2x improvement based on generation of the processor, and that's it. This benchmark doesn't seem to lend itself to SMT, so the multithreaded improvement is linear with cores and not threads. Are CPUs getting still getting better? Yes. But, not nearly as much better as I would bet the Phenom II compares to the original Athlon, a similar 10 year gap. |
hi, as attachment the result for a ryzen 3600, stock clock,
both single and multicore. Did not recompile your binary (seems make clean does not work) but should not be an issue since those are hardcrafted assembly.
Would be mayne interesting to compare with an compiler's optimized code..
3600single.txt
3600multi.txt
The text was updated successfully, but these errors were encountered: