• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Excel speed test comparison against an FX-8350

Page 9 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
I think there's probably a huge discrepancy based on version of Excel being used. Some 3570k scored 21 seconds, now my 4.5 GHz 5960x scores 35 seconds - But I'm using the 64 bit version of Excel 365, and he probably used Excel 2010.
 
Agreed, consistency of OS and Excel version is an issue with this. The model was originally written in Excel 2003. I was using Win7 and Excel 2007 when I started the thread. Now I'm using Win10 and Excel 2010. Did you turn off hyper-threading in the BIOS or Excel Options (HT is a big drag on the macro)?
 
John Tauwhare said:
Agreed, consistency of OS and Excel version is an issue with this. The model was originally written in Excel 2003. I was using Win7 and Excel 2007 when I started the thread. Now I'm using Win10 and Excel 2010. Did you turn off hyper-threading in the BIOS or Excel Options (HT is a big drag on the macro)?
Click to expand...

Interesting, I'll have to play with that on my 4770k system and see what combination scores the best.
 
I got this with my 4670k

Excel-_Speedtest-v1-dec24-2013-_CHART-_GHz-_Secs_zps.png
 
Last edited:
John Tauwhare said:
Agreed, consistency of OS and Excel version is an issue with this. The model was originally written in Excel 2003. I was using Win7 and Excel 2007 when I started the thread. Now I'm using Win10 and Excel 2010. Did you turn off hyper-threading in the BIOS or Excel Options (HT is a big drag on the macro)?
Click to expand...
No, it's a badly written benchmark.
 
Zstream said:
No, it's a badly written benchmark.
Click to expand...
You must be unfamiliar with VBA macros, as they also are all unoptimized. This benchmark is perfect as it represents exactly what is mostly ran on excel(Which is code made to just work, only sometimes optimized for speed). Someone who spends most their time working with these custom excel subroutines/functions appreciates how accurately this test reflects their true workload and is then able to avoid processors whose performance is sometimes 4 times slower than a comparable chip. I am really excited to see how Ryzen has stepped up its IPC and made AMD competitive, have yet to see how it performs on this benchmark.

Show me a better Excel benchmark that reflects true macro performance? Until then, this is my go to for comparisons to show coworkers and clients on what is slowing down there work.
 
cyrusfox said:
You must be unfamiliar with VBA macros, as they also are all unoptimized. This benchmark is perfect as it represents exactly what is mostly ran on excel(Which is code made to just work, only sometimes optimized for speed). Someone who spends most their time working with these custom excel subroutines/functions appreciates how accurately this test reflects their true workload and is then able to avoid processors whose performance is sometimes 4 times slower than a comparable chip. I am really excited to see how Ryzen has stepped up its IPC and made AMD competitive, have yet to see how it performs on this benchmark.

Show me a better Excel benchmark that reflects true macro performance? Until then, this is my go to for comparisons to show coworkers and clients on what is slowing down there work.
Click to expand...

No, what you're showing is what process works best in a mainly single threaded workload. In fact, it's doing a single sheet of calculations and moving on. If you want to know more, look at: http://analystcave.com/excel-vba-multithreading-tool/
 
Zstream said:
No, what you're showing is what process works best in a mainly single threaded workload. In fact, it's doing a single sheet of calculations and moving on.
Click to expand...

Which is exactly what's intended..
It doesn't have to be great Excel, in fact it shouldn't be; the objective is to assess CPU performance in a typical highly single threaded Excel workload, and for that it has proven to be fit for purpose.
 
Last edited:
John Tauwhare said:
Which is exactly what's intended..
It doesn't have to be great Excel, in fact it shouldn't be; the objective is to assess CPU performance in a typical highly single threaded Excel workload, and for that it has proven to be fit for purpose.

Images moved from Photobucket to postimg.org today on this thread (yawn).
Click to expand...

So you agree it's a poorly written benchmark.. gotcha. It's not a well thought out excel benchmark.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top