Why Einstein Takes Forever
5 Apr 2011 16:33:26 UTC
Topic 195736
(moderation:
With a 8GB RAM latest model 2.8 Intel i7 MACBOOK PRO and a 512 GB SSD running nearly 23 hrs a day, I just can't stand Einstein's projects taking several days to complete when SETI's run in less than a day. I've even put on hold every SETI project and left running just one Einstein and have only reached a 70% on the latest Einstein started after 3 days. No iTunes fellows, no time for music, just Skype and plain Safari for email with 14 hours of untouched lonely time for the computer every day, I mean, black screen; and it never goes to sleep. What's so special about Einstein to make it so slow?
Why Einstein Takes Forever
)
A Global Correlation search takes about 10 CPU hours on my Opteron 1210 running Linux at 1.8 GHz, not a particularly fast box. A Binary Pulsar search takes about 30 CPU hours, with no graphic board.
Tullio
Before I installed Gforce
)
Before I installed Gforce CUDA card a Global Corelation took about 17 hrs on my E5400 @ 2.7 GHz. A low end video card (GT 430) does one in 2 hrs. Your Seti times are about 6 times longer also. I would guess something is running in the background.
RE: With a 8GB RAM latest
)
I have a similarly configured Mac (mine is an iMac) and your CPU times and run times compare pretty favourably with mine. I get through a work unit in about 8 and a half hours - hyperthreaded.
http://einsteinathome.org/host/2412094/tasks
Perhaps someone can give you a technical explanation because your experience doesn’t seem to be right.
Verloren ist nur, wer sich selbst aufgibt. - Hans-Ulrich Rudel
RE: With a 8GB RAM latest
)
Go in and make sure your Mac is not snoozing on you, my wife just bought one similar to yours and hers was only taking about 8 hours per unit. You might also want to go into the Boinc Manager and change the setting to zero under Advanced, Preferences, processor usage and then where it says 'while processor usage is less than [25] percent (0 means no restriction)'. The default is 25 and that means that anytime your cpu is doing ANYTHING else and gets down to to only 25% free Boinc stops crunching. Change this to a zero, meaning Boinc will go back to using its internal task priority settings, and see if your processing times drop, if so play with this number until you get a balance of usability and crunching times. Boinc ALWAYS stops, or slows down its crunching, when the computer is doing something else due to the 'task priority' settings. But with this setting at 25% Boinc will not crunch at all if the cpu does not have more than that percentage of cpu free. It is adjustable to any number from 1 to 100, but at too high a number Boinc just won't ever crunch.
RE: The default is 25 and
)
It's the other way round ;-)
=> "anytime your cpu is doing ANYTHING else and gets down to to only 75% free Boinc stops crunching" if anything besides BOINC uses 25% or more, BOINC stops crunching.
Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
I am using default settings
)
I am using default settings on my two cores Opteron 1210 running Linux. I am running 6 BOINC projects, one of them a Virtual Machine plus another Virtual Machine which is not a BOINC project. They alternate easily, running three of them at the same time, two BOINC and another not BOINC. They all have the same priority (39) and the BOINC projects have equal share. The only problem I have is with AQUA@home, which is multithreading and takes 2 cores by itself, but the not BOINC Virtual Machine (Solaris) is still able to run.
Tullio
RE: RE: The default is 25
)
I always say that wrong, I know what I want to say it just doesn't come out right, thanks for fixing it!!
RE: ...SETI's run in less
)
Just to interject, be careful in comparing Work Units from different projects. There is no reason they should be the same in any way.
hi I have a NV 88 GT 512 m
)
hi
I have a NV 88 GT 512 m and the time remaining goes up and not down
making any project take even longer.
I'm running on an AMD dual core 6400+ 3.1 gh
RE: hi I have a NV 88 GT
)
Hi and welcome to E@H
The strange beahiour in "remaining time" display is caused by the fact that your PC seems to run its very first E@H units now. BOINC has to make an initial guess what the runtime will be, and if the guess is too optimistic, BOINC has to correct the estimation upwards as it crunches along.
Once more units are finished, BOINC will make better guesses of the required runtime as it collects statistics about the runtime of completed tasks).
HBE