As you may know, I've been working with pjkenned to expand on Musky's benchmark tool. The idea is that we take those captured work units, run them for a given number of frames, then upload them to a publicly accessible MySQL instance where anyone can browse/download/crunch the data thats there.
After a couple of false starts (what works great on an i7-860 didn't work properly on an i7-2600k - what worked greeat on those mis-reported on a dual Opteron .... ) I think it's at a point where more people can test it - I need to know what works, what breaks, when and how it breaks.
The benchmark is currently Windows only, but once I have the quirks ironed out of that, I'll be porting it to Linux - specifically Ubuntu - but can look to other distros as well.
Once the benchmark versions are built, I'm then looking to build a "FAHLog watcher" - rather than upload data just on benchmark units, parse the FAHlog.txt file, and everytime you finish a WU, the same WU & System data gets uploaded, for every WU you process.
The info I'm currently gathering is:
FAH Info:
RunDate, UserName, BenchLive, WU, NumFrames, MaxTPF, MinTPF, AverageTPF, BenchVer, FAHVer, FAHArgs
CPU Info:
CPUVendor,CPUCoreName,CPUCodeName,Freq,CPUSpec,CPU Multiplier, CPUFSB, Stepping, InstructionSets, CPUPackage,CPUID,eCPUID,NumProcs,NumCores, Numthreads, L1DataNum, L1DataSize, L1InstNum, L1InstSize, L2Num,L2Size,L3Num,L3Size,
Memory Info:
Memory, MemFreq, Numdimms, MemType, MemChannels, CASLatency, RAS2CASDelay, RASPrecharge, CycleTime, RowRefreshTime, CommandRate
Motherboard:
MoboVendor,MoboModel
OS Info:
Platform,Scheduler,Kernel,Architecture,FileSystem
Result Verification
Authenticity Hash
If there any suggestions of additional information that would be useful, desirable to have if possible, I'm open to ideas. For request to access the beta, PM pjkenned either here or at http://forums.servethehome.com
H.
After a couple of false starts (what works great on an i7-860 didn't work properly on an i7-2600k - what worked greeat on those mis-reported on a dual Opteron .... ) I think it's at a point where more people can test it - I need to know what works, what breaks, when and how it breaks.
The benchmark is currently Windows only, but once I have the quirks ironed out of that, I'll be porting it to Linux - specifically Ubuntu - but can look to other distros as well.
Once the benchmark versions are built, I'm then looking to build a "FAHLog watcher" - rather than upload data just on benchmark units, parse the FAHlog.txt file, and everytime you finish a WU, the same WU & System data gets uploaded, for every WU you process.
The info I'm currently gathering is:
FAH Info:
RunDate, UserName, BenchLive, WU, NumFrames, MaxTPF, MinTPF, AverageTPF, BenchVer, FAHVer, FAHArgs
CPU Info:
CPUVendor,CPUCoreName,CPUCodeName,Freq,CPUSpec,CPU Multiplier, CPUFSB, Stepping, InstructionSets, CPUPackage,CPUID,eCPUID,NumProcs,NumCores, Numthreads, L1DataNum, L1DataSize, L1InstNum, L1InstSize, L2Num,L2Size,L3Num,L3Size,
Memory Info:
Memory, MemFreq, Numdimms, MemType, MemChannels, CASLatency, RAS2CASDelay, RASPrecharge, CycleTime, RowRefreshTime, CommandRate
Motherboard:
MoboVendor,MoboModel
OS Info:
Platform,Scheduler,Kernel,Architecture,FileSystem
Result Verification
Authenticity Hash
If there any suggestions of additional information that would be useful, desirable to have if possible, I'm open to ideas. For request to access the beta, PM pjkenned either here or at http://forums.servethehome.com
H.