Einstein does not seem to relinquish the processor on the basis set in preferences.
25 Jul 2005 8:54:02 UTC
Topic 189601
(moderation:
I have found the after starting einstein on a machine also running seti, I had seti and einstein change every hour as required by preferences. A few dya later, however, Einstein took all the processing power until, at the moment, it is processing its last WU. It also does not request any more WU's. I have seen the bleat about no more WU's requested.
Is this because of shorter deadlines set for einstein that for seti, and if it is could the deadlines for Einsteins not perhaps be extended?
Einstein does not seem to relinquish the processor on the basis
)
Deadlines are based upon project and scientific need. In order to keep the project moving, Einstein requires a quicker return of results then SETI. This is because completed work plays a roll in what future work is created. This question has been asked many, many times, but for the foreseeable future, it doesn't look like extending the deadline is an option, at this point in the Einstein project. This is a popular request, but for now, quick return of finished work is the priority.
You might try reducing the size of your cache if it is too large. No more then 2-3 days, if you are running two projects.
It would also help if you mentioned which of your three computers you were experiencing this problem with, the OS, etc.
Team MacNN - The best Macintosh team ever.
RE: I have found the after
)
I am having the same problem and I tried reducing the days, did not work? ANyone else have any ideas? See Boinc 4.45 thread.
How long did you give for
)
How long did you give for your machine(s) to come to a steady state after the change? I usually see it level out in about a day or two, i've seen some people claim as high as a week to reach equilibrium.
Jim
RE: Deadlines are based
)
Hi,
I experienced the problem on all three of my machines. It did hit the slowest machine the soonest, while it hit the next fastest second and the fastest only after 2 or 3 days. I am running XP SP2 on the fastest, 2003 Server SP1 on the second and Linux (Fedora RC3) on the slowest. The real problem is that I don't know when they will start processing Einstein again. My second fastest machine has not requested Einstein WU's for the last two days while the slowest not in three days. I would guess that you would get more predictable flow of results if you extended the deadline to get a constant 50-50 split.
The real problem I guess is that the deadline is short, but the real processing time is three times as long as the seti WU's.
I am running 4 machine, 3 of
)
I am running 4 machine, 3 of which I can monitor easily. Of those 3, 2 are running CPDN, LHC, SETI, and Einstein. The 3rd is running LHC, SETI, and Einstein. They are all on a permanent connection. The slowest of the 3 is a 700 MHz Pentium III Laptop. I connect every 0.5 days. I run all projects at an equal resource share. I have a constant flow of work. All three work in round robin mode consistantly. The only time I have had EDF situation is when I attached to a new project, but BOINC quickly (within a day) got it's quota's fixed again.
Jim
Jim