the time interval of 1 grants of dispatches up to report deathline is absolutely too short!
i think that am either an error or a bad joke. many user still different projects have to run, surely not everything else will thus delete only at the time to keep.
please this tests
greet

GERMAN ORIGINAL:
zeit zum berechnen zu kurz!
die zeitspanne von 1 stunde vom versenden bis zur report deathline ist absolut zu kurz!
ich denke entweder ist das ein error oder ein schlechter scherz. viele user haben noch andere projekte laufen, werden also sicher nicht alles andere löschen nur um die zeit einzuhalten.
bitte prüft dies nach.
gruss

Not quite certain what the question is, but this project is currently handing out extremely short WUs. Usually less than 5 min / WU.

that is clear and goes also into order.
the problem is: I have further 3 projects to run and these change after in other in the hourly rythmus. to pirates to line up am those report deathline was exceeded. it uses nothing if wu free purged or is not not important the
indicated report deathline for the moment??
now more clearly which is I mean??
excuses my bad english
olli

german:
ja das ist klar und geht auch in ordnung.
das problem ist: ich habe weitere 3 projekte laufen und diese wechseln nacheinnander im stündlichen rythmus. bis pirates an der reihe ist wurde die report deathline überschritten. es nützt ja nichts wenn die wu unberechnet verfallen. oder ist die angegebene report deathline nicht wichtig im moment??
ist jetzt klarer was ich meine??
olli

I have noticed the same thing. I'm assuming the deadlines are so short because the WUs take almost no time to compute, they don't think it would take long to return the results. But like you said, if you are running other projects, you are almost guaranteed to miss the deadline.

They are still in very early testing stages right now, so I wouldn't worry about it.

> I have noticed the same thing. I'm assuming the deadlines are so short because
> the WUs take almost no time to compute, they don't think it would take long to
> return the results. But like you said, if you are running other projects, you
> are almost guaranteed to miss the deadline.


Well, I do not think there are many people who run only pirates@home which sends out work just occasionally.

> > I have noticed the same thing. I'm assuming the deadlines are so short
> because
> > the WUs take almost no time to compute, they don't think it would take
> long to
> > return the results. But like you said, if you are running other projects,
> you
> > are almost guaranteed to miss the deadline.
>
>
> Well, I do not think there are many people who run only pirates@home which
> sends out work just occasionally.
>
>
Some of their developers are probably running only Pirates. I know that I am running several others.

> > > I have noticed the same thing. I'm assuming the deadlines are so
> short
> > because
> > > the WUs take almost no time to compute, they don't think it would
> take
> > long to
> > > return the results. But like you said, if you are running other
> projects,
> > you
> > > are almost guaranteed to miss the deadline.

Granted that a "normal" project shouldn't have such a short deadline, certainly not less than or equal to the pre-emption cycle time, but possibly the BOINC CC scheduling policy should also be looked at a little more carefully. The CC needs to make sure that WU's get crunched and reported by their deadline. Resource shares can be re-balanced later by "simply" not downloading any new work for that project until other projects have had time to catch up. That should prevent projects from abusing clients with lots of short deadlines.

The report deadline is still just a couple of hours. Why don't you change it? It is difficult enough to get a P@H wu, but once you get one, it's even more difficult to return it on time.

Is there someone from the P@H team taking a look at the forums???? This question about short deadlines has been around for some time. Is somebody going to answer it?????

> > Is there someone from the P@H team taking a look at the forums???? This
> > question about short deadlines has been around for some time. Is
> somebody
> > going to answer it?????
>
> Yes, we do read the forums, and it's very valuable to have people telling us
> what they see from "out there". We can't respond to every post, and in fact
> the great thing about the forums is that users can share info and help each
> other. But I'll try to explain why the workunits are so short.
>
> We are not crunching, we are testing the code. We are testing new versions of
> the application (even if you don't see a difference in the screensaver) and we
> are testing server configuration and other "behind the scenes" things. We
> only send out a small batch of work to see how it does, and we want to get a
> response back fairily quickly if there are errors. For example, a file was
> deleted accidentally the other day so a whole batch of work failed because the
> file could not be downloaded. That showed up fairly quickly and we corrected
> it, but other errors may only show up at the end of the run. We don't want to
> wait 2 weeks to find out about it.
>
> It's been extremely valuable to have a pool of machines to run our tests.
> Even if your machine is busy crunching for SETI or LHC, someone's machine
> pickups up the work and sends it back within the deadline. Or if not, we get
> to see that what happens next is working.
>
> We did extend the deadllines to over 2 hours so that the 1 hour scheduler
> cycle would have more chance of getting something. We might extend the
> deadline further as needed, or make it shorter as part of our testing. It
> won't get as long as SETI just because we are not doing the same thing. And
> if your machine is crunching for SETI or LHC then it's doing useful work
> anyway.
>
> Pirates is a test, and a very valuable way for us to test things without
> anybody thinking that we are doing serious production. If you want to be
> ready for helping with production computing for Einstein@Home then please make
> sure you are signed up with the APS for notification. All I can say right
> now is that progress is being made on the real Einstein@Home, but nothing is
> open to outside users yet. When outside users are to be included they will be
> recruited from the APS mailing list. Be sure you have signed up!
>
> And thanks as always to all the Pirate crew for making your computers
> available to us. The credit you get on the scoreboard is no way near close
> to the true recognition you should get for letting us use your computers for
> this project.
>
>
It always seem to take about 6 to 12 hours for any of my machines to get around to the Pirates WU. Once the CPU actually gets them, they don't take that long. The CPU scheduler does not attempt to take deadlines into consideration. If it is at all possible, a 24 hour deadline would be appreciated. The download error reports would still come back immediately. I understand that 2 weeks is out.

Simply crank up the resource share on the Pirates project to a ridiculously high share in comparasion to the other projects. So if your other projects are in the low 100s, put pirates up to a share of 1000.

This does not become an issue because A.) The WUs are very small, and B.) if you are very concerned about Pirates preempting your other projects you wouldn't be running it. =)

Best,

David
Project Blue Book (PBB) D.C. Group
http://egroups.com/group/projectbluebookseti
____________