Conflicting titles for project configuration

Message boards : Questions and problems : Conflicting titles for project configuration
Message board moderation

To post messages, you must log in.

AuthorMessage
Jorge Ramos

Send message
Joined: 4 Sep 09
Posts: 16
Mexico
Message 47091 - Posted: 7 Jan 2013, 5:05:37 UTC

I have SETI and GPUGrid for projects. When selecting the "computing preferences" in each project, yields two different titles under the "Network usage" section. SETI reports as:

"Maintain enough tasks to keep busy for at least
(max 10 days).
"

while GPUGrid reports:

"Computer is connected to the Internet about every
Leave blank or 0 if always connected.
"

both will affect the same parameter but, obviously, they do not mean the same thing. I am having trouble configuring my client for GPU usage (posted in another thread) and debugging it becomes obscure when the 2 projects I am involved give different meanings to the same parameter.
ID: 47091 · Report as offensive
Jorge Ramos

Send message
Joined: 4 Sep 09
Posts: 16
Mexico
Message 47093 - Posted: 7 Jan 2013, 5:13:46 UTC - in response to Message 47091.  

As BOINC is the common platform for both SETI and GPUGrid, I posted here, but should I be posting this anywhere other place?
ID: 47093 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15483
Netherlands
Message 47096 - Posted: 7 Jan 2013, 5:47:45 UTC - in response to Message 47093.  

On the GPUGrid forums. They're using the old notation, for BOINC 6 and previous versions. The newer one is for BOINC 7 and up.

Where BOINC 6 would for instance report work and immediately ask a new task, BOINC 7.0 will try to store a couple of "ready to report" results, report them and immediately request work only when BOINC is under the value set by the Minimum work buffer.

This means that when you have left your old BOINC 6 values for "Connect to" + "Additional work" at, example given 0.1 and 1.0, that BOINC 7.0 will ask for 1.1 days worth of work and ONLY renew this cache when it's fallen under the 0.1 days worth of work limit.

Which means that it can happen that your BOINC runs empty, because 7.0 won't request new work before it has dropped below the 'minimum work' setting and will only ask for work up to the 'and additional' setting --and that only from the project that has the highest priority (worst REC to resource share ratio). Only if that project doesn't have work it will ask other projects in order of priority.
ID: 47096 · Report as offensive

Message boards : Questions and problems : Conflicting titles for project configuration

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.