5h return time ? what's that a PII@300 MHz ? or do you mean the time that pases befor your boinc client contacts the server ?

It does. So-called "panic mode". *grin*
But it would be bad if BOINC would go into constant panic mode and only crunch Milkyways and you don't get your other WUs finished.

Got 20 on my lappy as well but not on the other boxes. ;-(

I heard an unfounded rumor that I was somehow involved.

Yeah, and they even caught you on camera :P

see the pic:

The server has been out of work for nearly 24 hours now, and there are still over 5000 WUs out in the wind. Seems to me that if new work generation depends on the old results, the deadline should be shortened.

Maybe try 12 hours and see how that goes, at least if the WU ends up on a duffer, it would time out and possibly get sent to a faster, more reliable host.

.....Travis....Dave....wake up....

Nice paper Travis!

Question, the below paragraph seems to indicate the results returned quickest update the database and generate a new line to compute. If this is so, how useful are the slower computers as it seems their results as you said will be outdated when received. I would think a minimum "work unit crunch time" suggestion pointing out the "real time" model updating as a qualifier for computers for this project so people with slow units do not waste their time and your server space with outdated results would be needed.

In the first phase of the algorithm (while the population
size is less than the maximum population size) the server
is being initialized and a random population is generated.
When a request work message is processed, a random pa-
rameter set is generated, and when a report work message
is processed, the population is updated with the parameters
and the fitness of that evaluation. When enough report work
messages have been processed, the algorithm proceeds into
the second phase which performs the actual genetic search.
In the second phase, report work will insert the new pa-
rameters and their fitness into the population but only if
they are better than the worst current member and remove
the worst member if required to keep the population size
the same. Otherwise the parameters and the result are dis-
carded. Processing a request work message will either return
a mutation or reproduction (crossover) from the population.

I hope it works. :-P

Well since I jinxed us with that other post maybe if I say need more work it will work?

It's called the 'Post of Death' server subroutine..... :(

Seems to be common in alpha-beta projects....guess nobody has anything to say then and is a compliment to the administrators :D

Btw-nice to see!

Yes, would be a good workaround for the current situation! ;-)

this really needs looked at, and fixed

Yeah, we need to get rid of the FreeBSD as server OS ASAP (blame the labstaff for that one).. hopefully after spring break we'll ge that all sovled...

BTW... I'm getting mad without my daily dosis of Milkyway ;)

it should be genrating more work, you guys getting any yet?

Let us know if 1.19 is running that much faster on the windows environment -- if so we might have to reduce credit awarded to keep it in line with other projects.

Let us know if 1.19 is running that much faster on the windows environment -- if so we might have to reduce credit awarded to keep it in line with other projects.