Too big project chunks/work units

Bev & Bud Steighner
Bev & Bud Steighner
Joined: 14 Apr 07
Posts: 1
Credit: 1250
RAC: 0
Topic 193358

Suggestion-There needs to be smaller work units so the computer isn't working on a two day job (44 hour)...if the work unit is an hour or so, the user sees progress and doesn't abort (work restarts to zero if reboot, or suspended)what seems to be a huge task-...using a P4 HT 3.0 gig hertz, 1.5 gig mem-thanks

Mahbubur
Mahbubur
Joined: 31 Mar 06
Posts: 46
Credit: 258468
RAC: 0

Too big project chunks/work units

Quote:
Suggestion-There needs to be smaller work units so the computer isn't working on a two day job (44 hour)...if the work unit is an hour or so, the user sees progress and doesn't abort (work restarts to zero if reboot, or suspended)what seems to be a huge task-...using a P4 HT 3.0 gig hertz, 1.5 gig mem-thanks

But surely youd see progress with the progress bar in BOINC manager. As for 1hour work units, there would be huge problems of bandwidth usage and also current wu/core allocation.

Juan Carlos Alvaro
Juan Carlos Alvaro
Joined: 14 Dec 07
Posts: 4
Credit: 4913
RAC: 0

I agree, serious better than

I agree, serious better than they were smaller, not of one hour but neither of 40.

I believe that so big there are more possibilities of process errors. I have already had two.

Serious friendlier, if they are smaller.

A greeting

Pooh Bear 27
Pooh Bear 27
Joined: 20 Mar 05
Posts: 1376
Credit: 20312671
RAC: 0

Each project is unique and

Each project is unique and their data is also. The issue is that some data can not be made smaller. The data needs to be completed in a single phase, so they can not break it down any smaller for scientific reasons.

Comment viewing options

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