Ryzen Excel Benchmark Request

S

squeek88

n00b
Joined
Feb 6, 2016
Messages
2
Hi,

If anyone has the time, could they kindly run the attached Benchmark Excel 2013 sheet (there is a macro button at top left) and disclose the time taken (shown at the bottom status bar) on either a Ryzen 5 or 7, and if possible running ram at 2133 and then at highest possible speed like 3200+? My 12-core Xeon at 2133 takes approximately 5s FYI.

I'm trying to work out if the core deficient to my Xeon will be offset by faster ram, or will I need to go threadripper. Sometimes opening and closing big excel files can take 3mins and this also seems to be a memory intensive process. Thanks in advance for your time!
 

Attachments

  • Rank test.rar
    8.2 MB · Views: 27
1600x Stock w/3066 ram

9.65sec

For reference my work Phenom 2 x6 1045t

29.2sec
 
Just wanted to try this for fun, averages about 4.1 s on the sig rig running 64-bit Excel 2016.
 
Just for fun, this took 86 seconds on my i3-5005U work laptop. It was not happy. :-P
 
Using 1800x w/3200 mem, ran 5 x (Excel 2013)
9.06, 7.54, 9.38, 9.45, 9.14

Ran 5 times instead of 2 because of that second result.
 
On a old pentium dual core E5200 that sits in the print room it did the bench in 243sec painfully slow.
 
mvmiller12 said:
I just gotta say you guys are pretty brave running an Excel macro from a guy with only 26 posts in this forum...
Click to expand...

Yup, I was going to say the same thing.

I just hope this isn't going to be one of you guys...

05onfire1_xp-master768-v2.jpg
 
Well, you can look at the macro before you run it. It's about 10 lines of code that measures the time to refresh the worksheet, which generates a bunch of random numbers and then ranks them. If I didn't know my way around an excel macro I probably wouldn't run it.
 
bobzdar said:
Well, you can look at the macro before you run it. It's about 10 lines of code that measures the time to refresh the worksheet, which generates a bunch of random numbers and then ranks them. If I didn't know my way around an excel macro I probably wouldn't run it.
Click to expand...

Thanks all - yes the macro is just a timer. You could easily delete the macro and just insert your own timer. VBA is as old as the hills...

I'm really surprised by the results .. adjusting for cores I expected around 7-8s, so seems the ram was not that beneficial and the cores don't seem to communicate that well (the random number generation and ranking is independent so should scale by core very well), oh well the ram may help speed up opening and closing files.
 
Last edited:
You must log in or register to reply here.
Back
Top