"I go fast!1!11!1!"
- Oct 13, 2008
- 20,927 (6.24/day)
- IA, USA
|Processor||Intel Core i7-6700K (4 x 4.00 GHz) w/ HT and Turbo on|
|Motherboard||MSI Z170A GAMING M7|
|Memory||2 x Kingston HyperX DDR4-2133 8 GiB|
|Video Card(s)||PowerColor PCS+ 390 8 GiB DVI + HDMI|
|Storage||Crucial MX300 275 GB, Seagate 6 TB 7200 RPM|
|Display(s)||Samsung SyncMaster T240 24" LCD (1920x1200 HDMI) + Samsung SyncMaster 906BW 19" LCD (1440x900 DVI)|
|Case||Coolermaster HAF 932 w/ USB 3.0 5.25" bay|
|Audio Device(s)||Realtek Onboard, Micca OriGen+|
|Power Supply||Enermax Platimax 850w|
|Mouse||SteelSeries Sensei RAW|
|Software||Windows 10 Pro 64-bit|
|Benchmark Scores||Faster than the tortoise; slower than the hare.|
Also, auto cpu speed detection will be done when I feel like it.
The best I could come up with is grabbing it from the registry:
However, on my processor, it reports 1.6 GHz or 2.66 GHz when it should be 2.79 GHz.
Suggestion: Why not make the CPU do mock work that BOINC does, crunch a few numbers, then estimate it over x number of hours at y % CPU usage? That way, it would be processor indepenedant. You should have enough information to create a forumla that gets close.
As far as I know, a bunch of double precision multiply and divide should suffice for simulating work.