*After 1 hour cpu 10% done, Estimated 14 Hours to crunch a single WU
using app 4.58 on this host -> Pentium III 500 mhz http://einsteinathome.org/host/662689
I requested "no more work" ... When a faster app be in, I'll test again
*After 1 hour cpu 10% done, Estimated 14 Hours to crunch a single WU
using app 4.58 on this host -> Pentium III 500 mhz http://einsteinathome.org/host/662689
I requested "no more work" ... When a faster app be in, I'll test again
Thanks
It takes about 18 hours on my 400 MHz Pentium II running Linux. I have two pending results since people with much faster CPUs with Windows and Darwin have not yet terminated their work.
Tullio
I see that the anonymous platform scheme we use for public Beta Test is badly prepared for the transition to S5R1 we're doing now.
With that transition I'd consider the Beta Test to be over - and successful. The Apps we will use for S5R1 are almost the same than the ones we had in public Beta Test, the improved science code is actually identical, thus the new Apps will be precisely as fast as the Beta Test Apps.
Thank you for all your help, this was incredibly useful!
However the Beta Test Apps are lacking some features we found we need for the new run, and thus can't be used for the new Workunits. There is a bit of S4 work left, but no guarantee that the scheduler will try to give it to your machine. So
- if you want to keep your machines busy regardless of the type of work processed, just remove the app_info.xml file (and restart the client). You will download the new App for the new work, and the old official App for the old S4 work.
- if you prefer to do the old S4 work while it is available and risk your machine runs dry, keep the app_info.xml until there's no more S4 work left (we'll add an entry for that on the server status page).
- if you want to live risky and enjoy it, try the following: remove the app_info.xml, but keep a copy of the Beta App executables somewhre outside the project directory. Restart the client. After getting S4 work and having downloaded the old official App, stop the client again and replace the executables of the official App with the backups of the Beta Test App. Then start the client again. There's no guarantee that this will fool all clients on all machines, but it should work most of the time and finish the S4 work with the speed of the Beta Apps.
http://einstein.phys.uwm.edu/
)
http://einsteinathome.org/task/33119956
*After 1 hour cpu 10% done, Estimated 14 Hours to crunch a single WU
using app 4.58 on this host -> Pentium III 500 mhz
http://einsteinathome.org/host/662689
I requested "no more work" ... When a faster app be in, I'll test again
Thanks
Click signature for global team stats
RE: http://einstein.phys.uw
)
It takes about 18 hours on my 400 MHz Pentium II running Linux. I have two pending results since people with much faster CPUs with Windows and Darwin have not yet terminated their work.
Tullio
I see that the anonymous
)
I see that the anonymous platform scheme we use for public Beta Test is badly prepared for the transition to S5R1 we're doing now.
With that transition I'd consider the Beta Test to be over - and successful. The Apps we will use for S5R1 are almost the same than the ones we had in public Beta Test, the improved science code is actually identical, thus the new Apps will be precisely as fast as the Beta Test Apps.
Thank you for all your help, this was incredibly useful!
However the Beta Test Apps are lacking some features we found we need for the new run, and thus can't be used for the new Workunits. There is a bit of S4 work left, but no guarantee that the scheduler will try to give it to your machine. So
- if you want to keep your machines busy regardless of the type of work processed, just remove the app_info.xml file (and restart the client). You will download the new App for the new work, and the old official App for the old S4 work.
- if you prefer to do the old S4 work while it is available and risk your machine runs dry, keep the app_info.xml until there's no more S4 work left (we'll add an entry for that on the server status page).
- if you want to live risky and enjoy it, try the following: remove the app_info.xml, but keep a copy of the Beta App executables somewhre outside the project directory. Restart the client. After getting S4 work and having downloaded the old official App, stop the client again and replace the executables of the official App with the backups of the Beta Test App. Then start the client again. There's no guarantee that this will fool all clients on all machines, but it should work most of the time and finish the S4 work with the speed of the Beta Apps.
Have fun!
BM
BM