Message boards :
Server and website :
fast result returns
Message board moderation
Previous · 1 · 2
| Author | Message |
|---|---|
|
Send message Joined: 18 Apr 14 Posts: 43 Credit: 1,192,135,172 RAC: 0 Level ![]() Scientific publications ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]()
|
After missing a deadline by 20 minutes I was looking at changing my work unit buffer anyway. Just because the bonus will still be granted within 24 hours, it makes sense to choose the buffer as small as possible. The time is counting after the WU's download. So if the WU is boring on your hard drive, valuable points are wasted. Therefore, I have chosen this setting (0,01 days): Regards, Josef
|
|
Send message Joined: 15 Apr 14 Posts: 5 Credit: 6,433,630 RAC: 0 Level ![]() Scientific publications
|
Good to know. For a laptop I have a relatively fast crunching GPU, but even on "short" runs the length seems to vary. I've had some take 8 hours others closer to 20. The longer ones are credited better, but if they push too long I won't be fast enough to get the bonus. Currently testing now with a NOELIA task estimated for 36 hours. Its actually at 13% with 2 hours in, so, if THAT holds steady, it should be done in 16 hours from arrival On the CPU end, which I use for other projects, the shorter buffer is helping collect a variety of tasks, but it still seems to want to complete shorter deadlines first, and let long deadline projects sit around for days. The resource share setting seems useless in affecting this, so I'm suspending projects manually if they take too much CPU time |
©2026 Universitat Pompeu Fabra