About half the old posts are still in the Google cache. Should we grab them and re-post?
Result List:
I'll start by listing them all on this thread (on my first post.)
I'll keep track of the top few times on each size. But I won't split them into different binaries (x86 vs. x64) because that would be too much. (Yes, let 64-bit rule!!!)
Change Threads:
Yes I can bring that back. But it can only have 2 modes: 1 thread, or threads >= cores (first power of 2 that's >= # of cores).
This is because of the way the program uses more threads than selected, so "extra cores" will skew results. There's no way I can enforce CPU affinity.
Efficiency Number:
Yes I can do that. But keep in mind that it won't scale across different sizes and # of cores.
Computing Pi isn't linear. It's roughly O( n*log(n)^3 ). So larger computations will have lower efficiency.
Also, the program doesn't quite scale linearly with the # of cores. So multi-threaded benchmarks will have lower efficiency.
Aside from that:
The next version, will use less memory. 1 billion digits will only require 5.25GB as opposed to 5.98GB of ram in the current release. Which means that it'll be possible for the "standard" Core i7 with 6GB of ram to bench 1 billion digits.
For the "very large" end, 10 billion digits will require 52.9 GB of ram (in the new version). By the looks of it, I "might" be able to squeeze that down to 46GB - which would make it possible for a fully-loaded 12-slot Gainestown server to do. And THAT would be interesting...
Anyways... Post your benchmarks everyone!!!
Bookmarks