Forum > Windows

Windows optimized SETI@Home science apps - Release 1.3

(1/2) > >>

Simon:
Along with the automatic test and installer package, I've updated the downloads to Release 1.3 of the science applications.

This update is a cosmetic fix - it inserts information about the true CPU speed into the stderr section of each result.
An example - my Pentium D says it's a 2.66 GHz CPU and BOINC records this information. It actually runs at 3.85 GHz, though (it's overclocked).

Monza_MH26 suggested it's a good idea to show the real CPU speed as well - I agree and added it.

Regards,
Simon.

Kna:
Just a suggestion :  modify your naming conventions to incorporate the release version, something like that to keep the filenames not too long  ?

 setiathome-5.15-kwsn-mmx.exe  ->  S@H-5.15-kwsn-1.3-mmx.exe

Simon:
Been thinking about that, too - sounds good. Have t think about it a little more :)

Regards,
Simon.

Josef W. Segur:

--- Quote from: Simon on 13 Jul 2006, 03:20:32 am ---Monza_MH26 suggested it's a good idea to show the real CPU speed as well - I agree and added it.
--- End quote ---

Noting  actual clock is very good, particularly for system comparison. If the measurement routine is light enough, it might also be used to get an average clock by measuring periodically (perhaps when checkpoints are written). Summing those measurements and keeping a count would allow showing the average clock raste.

For those crunching on laptops which are on battery sometimes or even desktops with marginal cooling causing CPU slowdowns, that average rate might be more meaningful.

Simon:
It's using an IPP function -


--- Code: ---#ifdef USE_IPP
    int myfreq;
    ippGetCpuFreqMhz(&myfreq);
    fprintf(stderr,"CPU real speed: %d MHz\n\n",myfreq);
#endif
--- End code ---

This is what I inserted into the code. No idea how heavy the overhead for that function is, but I believe it's very small.

Regards,
Simon.

Navigation

[0] Message Index

[#] Next page