deadlines are too short

Henry Tsai
Henry Tsai
Joined: 28 Sep 10
Posts: 3
Credit: 887533
RAC: 315
Topic 196488

Hi,
My computer runs both Seti and Einstein. Sometime the job piece from Einstein requires 60+ hours to calculate, but deadline is only two weeks, so jobs from Einstein are frequently run in "high priority" which displaces other job pieces in the Boinc. Can you make the job pieces smaller or extend their deadlines? so, every job has a chance to be done regularly?

Alex
Alex
Joined: 1 Mar 05
Posts: 451
Credit: 502884979
RAC: 40083

deadlines are too short

One possible solution is to decrease your workbuffer size in the settings (usage of network)

Jord
Joined: 26 Jan 05
Posts: 2952
Credit: 5779100
RAC: 0

Just don't run BRP4s on your

Just don't run BRP4s on your i3, you can select which work you want to run in the project preferences.

Run only the selected applications
Binary Radio Pulsar Search (Arecibo)
Gravitational Wave S6 LineVeto search
Gamma-ray pulsar search #1


Check only the Gravitational Wave S6 LineVeto search, these are the shortest.

Mind, the 60+ hours that it shows is an estimate. As you've seen from the one you ran, it runs for about 127,320 seconds or ~35 hours. BOINC will need to run a couple of these before it learns how long these tasks are and then it will stop running them in panic mode. You just have to have patience about that. Or not run these tasks, if you can't have the patience.

I have run Einstein on a i3-530, all available work, for about a year. My BOINC was set to only do calculations between 9pm and 7am, to save electricity. It never missed a deadline on any of the projects that I ran.

Bikeman (Heinz-Bernd Eggenstein)
Bikeman (Heinz-...
Moderator
Joined: 28 Aug 06
Posts: 3522
Credit: 692140497
RAC: 17866

RE: Hi, Can you make the

Quote:
Hi,
Can you make the job pieces smaller or extend their deadlines?

We cannot make BRP4 jobs arbitarily short, for the following reason: BRP tasks may be scheduled to ither CPUs or GPUs, he workunits and results are the same). While one of those can take 30+ hours on your CPU, they run only about 900 seconds or less (15 minutes) on a very fast GPU. if we made the tasks even smaller, our project server would be overwhelmed with scheduler requests to submit finished work and request new work by those fast GPU hosts.

So unfortunately we cannot help from this end, and I suggest to follow Jord's advise.

Cheers
HB

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.