I noticed that I am getting no work in WCG and Rosetta.

I see the following in cc_config.xml for WCG

<client_version_check_url>http://www.worldcommunitygrid.org/download.php?xml=1</client_version_check_url>
<client_download_url>http://www.worldcommunitygrid.org/download.php</client_download_url>
<network_test_url>http://www.ibm.com/</network_test_url>
<start_delay>120</start_delay>

I see nothing in cc_config.xml for Rosetta

I just went into BOINC Manager and clicked on Update for WCG, and got the following messages:

12/2/2009 2:34:51 PM World Community Grid update requested by user
12/2/2009 2:34:51 PM World Community Grid Sending scheduler request: Requested by user.
12/2/2009 2:34:51 PM World Community Grid Not reporting or requesting tasks
12/2/2009 2:34:57 PM World Community Grid Scheduler request completed

and for Rosetta:

12/2/2009 2:51:52 PM rosetta@home update requested by user
12/2/2009 2:51:56 PM rosetta@home Sending scheduler request: Requested by user.
12/2/2009 2:51:56 PM rosetta@home Not reporting or requesting tasks
12/2/2009 2:52:02 PM rosetta@home Scheduler request completed



In WCG, DCF = 1.7057
CPU scheduling priority = 0
CPU work fetch priority = -175100.05
No deferrals

In Rosetta, DCF = 0.7622
CPU scheduling priority = 0
CPU work fetch priority = -113317.41
No deferrals

Connect about every = 0.20 Additional work buffer = 0.10. So, I think LTD = -207360.00, thus WCG and Rosetta are both higher.

I do have other projects:
Leiden:
DCF 1.2348
CPU scheduling priority = 6312
CPU work fetch priority = -63928
No deferrals

Docking:
DCF 1.0057
CPU scheduling priority = 5246
CPU work fetch priority = -86684.49
No deferrals

Einstein:
DCF 1.3515
CPU scheduling priority = 5720.19
CPU work fetch priority = -66072.27
No deferrals

SETI:
DCF 0.8379
CPU scheduling priority = -76925
CPU work fetch priority= -132907
No deferrals

Milkyway
DCF 1.8546
CPU scheduling priority = 59024.84
CPU work fetch priority = 0.00
No deferrals

The fact that I can know to present all of these numbers does not imply that I have the vaguest idea of what they all mean, except that a smaller negative number for CPU fetch compared to the negative expression of LTD means I should get work in the order of the highest difference first, and I do know that debt gets paid off.

This is a new machine, running 6.10.18, Win 7 64bit, I7-920, eight cores, GPU turned off in cc_config.xml. I have been running it for about three weeks, except for being away for the holiday. I started with default prefs but had nothing but trouble. I have gotten great help from CA's, mostly at WCG. I tried several different builds. I am finally getting somewhere. The machine has been running since Sunday night with no "out of work" periods.

I am set on Run always and Network activity always available. I know all of the prefs work together. I do not know if I have the best selection. I have been fiddling with the prefs a lot trying to get things to be smooth, but staying away from the machine for hours at a time to let BOINC sort itself out.

Re: Activity settings - the machine is always on when I am not at work. Work is two days per week, for about 10 hours per day. In turn off all four computers when I am at work because of our patch-and-pray electric company. Otherwise the machine is always on and connected to the internet. The other three machines, two Vista one XP, are set at default prefs are are doing just fine.

If any knowledgeable souls can better explain what I should be doing with Connect about and/or Additional work, whether Activity should remain Always or should revert to local prefs, I would be most happy to be educated.

---

http://sciencesprings.wordpress.com
http://facebook.com/sciencesprings

When you open BOINC Manager->Advanced view->Projects tab, what is the status for WCG and Rosetta?

---

The Status column is empty for all projects.

---

http://sciencesprings.wordpress.com
http://facebook.com/sciencesprings

Rob, do you know whether or not a WCG version of BOINC adds those entries to the cc_config.xml file? Or did you and Ingleside help mitrichr to add those while you helped him at the WCG forums?

<client_version_check_url>http://www.worldcommunitygrid.org/download.php?xml=1</client_version_check_url>
<client_download_url>http://www.worldcommunitygrid.org/download.php</client_download_url>
<network_test_url>http://www.ibm.com/</network_test_url>

---

Well, I certainly regret that I am irritating you, you have been nothing but patient, Sekerob.

But,

Regarding "How much elapsed time does the already buffered work PLUS the still to complete work add up to?" If more than 0.1+0.2 you got your answer." Where would I see this elapsed time figure, to know what it adds up to?

And, yes, I am not out of work; but that does not mean that I have my preferences properly set. It just means that I have not totally screwed them up. So, I still want to know, do the settings look O.K., should I have the Activity settings on Always? And how does the Connect about .2 and the Additional work buffer .1 differ from the default of 0.30 for Connect about?

I am sorry to be such a pain; but I want to get this right. Also, maybe in setting me straight on these things, you will also be answering questions for other people who have been or are searching the forums for existing threads dealing with these issues.

---

http://sciencesprings.wordpress.com
http://facebook.com/sciencesprings

Where would I see this elapsed time figure, to know what it adds up to?

Perhaps in the "To completion" column in Tasks tab? You'll have to select "Show all tasks" though.

Gruß,
Gundolf

Thanks for that... Since mitrichr is using BOINC 6.10.18 it will ignore those entries as it doesn't know about them and only report on them if the <unparsed_xml> flag is on. Was just checking. :)

The <start_delay> entry will work, though.

---

So, according to Sek, I have "no problem". Not true. When I left for work at 6:30AM, I had eight CPU cores crunching away. I had several WU's waiting to run, several waiting to start. Everything looked good.

When I arrived home at 4:30PM, I had been out of work since 1:46PM. My settings had been Connect about every 0.20 and Additional work buffer 0.10. My activity setting were Run always and Network activity always available. I asked if this was correct, no one answered me. I suspect it was incorrect.

I read that if one sets activity at Run Always and Network activity always available one should set Connect about every to 0.00. I read nothing about Additional work buffer.

So, I am asking again, what is the proper alignment of these settings?
In spite of the clock readings in Tasks, this machine is blowing through most WU's on CPU cores only in 2.5 to 3 hours, which I believe is equivalent to Connect every of .125. Should I lower Connect every to 0.10? Should I increase the Additional work buffer? If I am using these prefs, should I have Activity set on Run based on preferences and Network activity based on preferences?

Upon rebooting, I got a couple of WU's.

Here are the current messages since the reboot:

12/3/2009 5:00:40 PM Starting BOINC client version 6.10.18 for windows_x86_64
12/3/2009 5:00:40 PM Config: don't use coprocessors
12/3/2009 5:00:40 PM log flags: file_xfer, sched_ops, task
12/3/2009 5:00:40 PM Libraries: libcurl/7.19.4 OpenSSL/0.9.8l zlib/1.2.3
12/3/2009 5:00:40 PM Data directory: C:\ProgramData\BOINC
12/3/2009 5:00:40 PM Running under account mitrich
12/3/2009 5:00:40 PM Processor: 8 GenuineIntel Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz [Intel64 Family 6 Model 26 Stepping 5]
12/3/2009 5:00:40 PM Processor: 256.00 KB cache
12/3/2009 5:00:40 PM Processor features: fpu tsc pae nx sse sse2 pni
12/3/2009 5:00:40 PM OS: Microsoft Windows 7: Home Premium x64 Edition, (06.01.7600.00)
12/3/2009 5:00:40 PM Memory: 5.99 GB physical, 11.98 GB virtual
12/3/2009 5:00:40 PM Disk: 688.67 GB total, 651.29 GB free
12/3/2009 5:00:40 PM Local time is UTC -5 hours
12/3/2009 5:00:40 PM SETI@home Application uses missing NVIDIA GPU
12/3/2009 5:00:40 PM Not using a proxy
12/3/2009 5:00:40 PM rosetta@home URL http://boinc.bakerlab.org/rosetta/; Computer ID 1193569; resource share 100
12/3/2009 5:00:40 PM Leiden Classical URL http://boinc.gorlaeus.net/; Computer ID 70645; resource share 100
12/3/2009 5:00:40 PM Docking@Home URL http://docking.cis.udel.edu/; Computer ID 49828; resource share 100
12/3/2009 5:00:40 PM Einstein@Home URL http://einstein.phys.uwm.edu/; Computer ID 2175111; resource share 100
12/3/2009 5:00:40 PM Milkyway@home URL http://milkyway.cs.rpi.edu/milkyway/; Computer ID 120448; resource share 100
12/3/2009 5:00:40 PM SETI@home URL http://setiathome.berkeley.edu/; Computer ID 5176486; resource share 100
12/3/2009 5:00:40 PM World Community Grid URL http://www.worldcommunitygrid.org/; Computer ID 1106276; resource share 200
12/3/2009 5:00:40 PM rosetta@home General prefs: from rosetta@home (last modified 03-Dec-2009 16:54:27)
12/3/2009 5:00:40 PM rosetta@home Computer location: home
12/3/2009 5:00:40 PM General prefs: using separate prefs for home
12/3/2009 5:00:40 PM Reading preferences override file
12/3/2009 5:00:40 PM Preferences limit memory usage when active to 2454.00MB
12/3/2009 5:00:40 PM Preferences limit memory usage when idle to 4601.24MB
12/3/2009 5:00:40 PM Preferences limit disk usage to 30.00GB
12/3/2009 5:00:40 PM Suspending computation - initial delay
12/3/2009 5:02:43 PM World Community Grid Restarting task my794_00048_8 using hpf2 version 603
12/3/2009 5:02:43 PM Leiden Classical Restarting task wu_78596477_1257325319_51547_2 using classical version 556
12/3/2009 5:02:44 PM World Community Grid Sending scheduler request: To fetch work.
12/3/2009 5:02:44 PM World Community Grid Requesting new tasks
12/3/2009 5:02:49 PM World Community Grid Scheduler request completed: got 1 new tasks
12/3/2009 5:02:51 PM World Community Grid Starting my794_00066_17
12/3/2009 5:02:51 PM World Community Grid Starting task my794_00066_17 using hpf2 version 603
12/3/2009 5:10:41 PM Milkyway@home update requested by user
12/3/2009 5:10:45 PM Milkyway@home Sending scheduler request: Requested by user.
12/3/2009 5:10:45 PM Milkyway@home Reporting 6 completed tasks, not requesting new tasks
12/3/2009 5:10:50 PM Milkyway@home Scheduler request completed
12/3/2009 5:11:06 PM Docking@Home update requested by user
12/3/2009 5:11:11 PM Docking@Home Sending scheduler request: Requested by user.
12/3/2009 5:11:11 PM Docking@Home Reporting 2 completed tasks, not requesting new tasks
12/3/2009 5:11:16 PM Docking@Home Scheduler request completed
12/3/2009 5:11:22 PM Einstein@Home update requested by user
12/3/2009 5:11:26 PM Einstein@Home Sending scheduler request: Requested by user.
12/3/2009 5:11:26 PM Einstein@Home Reporting 2 completed tasks, not requesting new tasks
12/3/2009 5:11:31 PM Einstein@Home Scheduler request completed
12/3/2009 5:11:36 PM rosetta@home update requested by user
12/3/2009 5:11:41 PM rosetta@home Sending scheduler request: Requested by user.
12/3/2009 5:11:41 PM rosetta@home Not reporting or requesting tasks
12/3/2009 5:11:46 PM rosetta@home Scheduler request completed
12/3/2009 5:12:02 PM SETI@home update requested by user
12/3/2009 5:12:07 PM SETI@home Sending scheduler request: Requested by user.
12/3/2009 5:12:07 PM SETI@home Reporting 2 completed tasks, not requesting new tasks
12/3/2009 5:12:12 PM SETI@home Scheduler request completed

---

http://sciencesprings.wordpress.com
http://facebook.com/sciencesprings

My activity setting were Run always and Network activity always available. I asked if this was correct, no one answered me. I suspect it was incorrect.

I read that if one sets activity at Run Always and Network activity always available one should set Connect about every to 0.00. I read nothing about Additional work buffer.

By setting Run Always and Network activity always available, you override any preferences you set on them. So you override the Connect to of 0.20.

The Additional Buffer isn't overridden as it's got nothing to do with the actual Run or Connect preferences, only with how much cache you want to hold.

Now usually when you don't request more work, BOINC thinks you have enough in cache, or the project you're trying to update on has too much debt towards the other projects that are eligible to fetch work and that do have work.

You still have your cc_config.xml file?

<cc_config>
<log_flags>
<sched_op_debug>1</sched_op_debug>
<debt_debug>1</debt_debug>
<work_fetch_debug>1</work_fetch_debug>
</log_flags>
</cc_config>

Then exit BOINC & restart it, run for about 2 minutes. This will output quite a lot of lines. Suspend BOINC, copy out the messages (all of them), post them here.

When done, change to <debt_debug>0</debt_debug> and <work_fetch_debug>0</work_fetch_debug>, save file, BOINC Manager->Advanced->Read config file and resume BOINC. (yes, leave <sched_op_debug> on, as it will tell you and us a lot more in the future!)

---

Hey Jord-

First here is the cc_config.xml file

<cc_config>
<log_flags>
</log_flags>
<options>
<client_version_check_url>http://www.worldcommunitygrid.org/download.php?xml=1</client_version_check_url>
<client_download_url>http://www.worldcommunitygrid.org/download.php</client_download_url>
<network_test_url>http://www.ibm.com/</network_test_url>
<start_delay>120</start_delay>
<no_gpus>1</no_gpus>
</options>
</cc_config>

It does not read at all the way the file you presented reads. Is this file itself the problem, or does it indicate the problem?

>>RSM

---

http://sciencesprings.wordpress.com
http://facebook.com/sciencesprings

I meant to add in my lines, or to temporarily replace my cc_config.xml file with yours. Adding them into your cc-config.xml will make yours look like this:

<cc_config>
<log_flags>
<sched_op_debug>1</sched_op_debug>
<debt_debug>1</debt_debug>
<work_fetch_debug>1</work_fetch_debug>
</log_flags>
<options>
<client_version_check_url>http://www.worldcommunitygrid.org/download.php?xml=1</client_version_check_url>
<client_download_url>http://www.worldcommunitygrid.org/download.php</client_download_url>
<network_test_url>http://www.ibm.com/</network_test_url>
<start_delay>120</start_delay>
<no_gpus>1</no_gpus>
</options>
</cc_config>

By the way, the <client_version_check_url>, <client_download_url> and <network_test_url> lines are not needed in Berkeley BOINC. They're added there by WCG BOINC and only used by their client. They're not used by your BOINC 6.10.18

The <start_delay> line is used by BOINC 6.10.18, it suspends BOINC for 2 minutes when BOINC starts. It's primarily used to wait with crunching when BOINC starts up at the OS start.

---

Jord-

BOINC was started, run a bit over two minutes until I thought I saw everything from the three debugging lines. I hope this is correct:

12/3/2009 7:09:04 PM Starting BOINC client version 6.10.18 for windows_x86_64
12/3/2009 7:09:04 PM Config: don't use coprocessors
12/3/2009 7:09:04 PM log flags: file_xfer, sched_ops, task, debt_debug, sched_op_debug, work_fetch_debug
12/3/2009 7:09:04 PM Libraries: libcurl/7.19.4 OpenSSL/0.9.8l zlib/1.2.3
12/3/2009 7:09:04 PM Data directory: C:\ProgramData\BOINC
12/3/2009 7:09:04 PM Running under account mitrich
12/3/2009 7:09:05 PM Processor: 8 GenuineIntel Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz [Intel64 Family 6 Model 26 Stepping 5]
12/3/2009 7:09:05 PM Processor: 256.00 KB cache
12/3/2009 7:09:05 PM Processor features: fpu tsc pae nx sse sse2 pni
12/3/2009 7:09:05 PM OS: Microsoft Windows 7: Home Premium x64 Edition, (06.01.7600.00)
12/3/2009 7:09:05 PM Memory: 5.99 GB physical, 11.98 GB virtual
12/3/2009 7:09:05 PM Disk: 688.67 GB total, 651.19 GB free
12/3/2009 7:09:05 PM Local time is UTC -5 hours
12/3/2009 7:09:05 PM SETI@home Application uses missing NVIDIA GPU
12/3/2009 7:09:05 PM Not using a proxy
12/3/2009 7:09:05 PM rosetta@home URL http://boinc.bakerlab.org/rosetta/; Computer ID 1193569; resource share 100
12/3/2009 7:09:05 PM Leiden Classical URL http://boinc.gorlaeus.net/; Computer ID 70645; resource share 100
12/3/2009 7:09:05 PM Docking@Home URL http://docking.cis.udel.edu/; Computer ID 49828; resource share 100
12/3/2009 7:09:05 PM Einstein@Home URL http://einstein.phys.uwm.edu/; Computer ID 2175111; resource share 100
12/3/2009 7:09:05 PM Milkyway@home URL http://milkyway.cs.rpi.edu/milkyway/; Computer ID 120448; resource share 100
12/3/2009 7:09:05 PM SETI@home URL http://setiathome.berkeley.edu/; Computer ID 5176486; resource share 100
12/3/2009 7:09:05 PM World Community Grid URL http://www.worldcommunitygrid.org/; Computer ID 1106276; resource share 200
12/3/2009 7:09:07 PM rosetta@home General prefs: from rosetta@home (last modified 03-Dec-2009 16:54:27)
12/3/2009 7:09:07 PM rosetta@home Computer location: home
12/3/2009 7:09:07 PM General prefs: using separate prefs for home
12/3/2009 7:09:07 PM Reading preferences override file
12/3/2009 7:09:07 PM Preferences limit memory usage when active to 2454.00MB
12/3/2009 7:09:07 PM Preferences limit memory usage when idle to 4601.24MB
12/3/2009 7:09:09 PM Preferences limit disk usage to 30.00GB
12/3/2009 7:09:09 PM [work_fetch_debug] Request work fetch: Prefs update
12/3/2009 7:09:09 PM [work_fetch_debug] Request work fetch: Startup
12/3/2009 7:09:09 PM Suspending computation - initial delay
12/3/2009 7:09:09 PM [work_fetch_debug] Request work fetch: Backoff ended for rosetta@home
12/3/2009 7:09:09 PM [work_fetch_debug] Request work fetch: Backoff ended for Leiden Classical
12/3/2009 7:09:09 PM [work_fetch_debug] Request work fetch: Backoff ended for Docking@Home
12/3/2009 7:09:09 PM [work_fetch_debug] Request work fetch: Backoff ended for Einstein@Home
12/3/2009 7:09:09 PM [work_fetch_debug] Request work fetch: Backoff ended for Milkyway@home
12/3/2009 7:09:09 PM [work_fetch_debug] Request work fetch: Backoff ended for SETI@home
12/3/2009 7:09:09 PM [work_fetch_debug] Request work fetch: Backoff ended for World Community Grid
12/3/2009 7:11:05 PM [debt_debug] adjust_debt: elapsed time (120) longer than sched enforce period(60). Ignoring this period.
12/3/2009 7:11:08 PM World Community Grid Restarting task my794_00048_8 using hpf2 version 603
12/3/2009 7:11:08 PM World Community Grid Restarting task my794_00066_17 using hpf2 version 603
12/3/2009 7:11:08 PM World Community Grid Restarting task R00456_716b8958d798a1c23623e298e9ace825_00_1 using rice version 617
12/3/2009 7:11:08 PM Leiden Classical Restarting task wu_649415041_1259566727_5349_1 using trajtou-pd110paw version 540
12/3/2009 7:11:08 PM Leiden Classical Restarting task wu_649415041_1259566727_5343_2 using trajtou-pd110paw version 540
12/3/2009 7:11:09 PM World Community Grid Restarting task faah9349_ZINC11586429_xJ1_xtal_00_0 using faah version 607
12/3/2009 7:11:10 PM Docking@Home Restarting task 1k1m_51_mod0014trypsin_11547_443765_0 using charmm34 version 623
12/3/2009 7:11:10 PM World Community Grid chosen: CPU idle instance
12/3/2009 7:11:10 PM [wfd] ------- start work fetch state -------
12/3/2009 7:11:10 PM [wfd] target work buffer: 17280.00 + 8640.00 sec
12/3/2009 7:11:10 PM [wfd] CPU: shortfall 93319.64 nidle 1.00 saturated 0.00 busy 0.00 RS fetchable 800.00 runnable 400.00
12/3/2009 7:11:10 PM rosetta@home [wfd] CPU: fetch share 0.13 debt -14574.02 backoff dt 0.00 int 0.00
12/3/2009 7:11:10 PM Leiden Classical [wfd] CPU: fetch share 0.13 debt -12875.15 backoff dt 0.00 int 0.00
12/3/2009 7:11:10 PM Docking@Home [wfd] CPU: fetch share 0.13 debt -13396.32 backoff dt 0.00 int 0.00
12/3/2009 7:11:10 PM Einstein@Home [wfd] CPU: fetch share 0.13 debt -36665.30 backoff dt 0.00 int 0.00
12/3/2009 7:11:10 PM Milkyway@home [wfd] CPU: fetch share 0.13 debt -92723.23 backoff dt 0.00 int 0.00 (overworked)
12/3/2009 7:11:10 PM SETI@home [wfd] CPU: fetch share 0.13 debt -36254.30 backoff dt 0.00 int 0.00
12/3/2009 7:11:10 PM World Community Grid [wfd] CPU: fetch share 0.25 debt 0.00 backoff dt 0.00 int 0.00
12/3/2009 7:11:10 PM rosetta@home [wfd] overall_debt -14574
12/3/2009 7:11:10 PM Leiden Classical [wfd] overall_debt -12875
12/3/2009 7:11:10 PM Docking@Home [wfd] overall_debt -13396
12/3/2009 7:11:10 PM Einstein@Home [wfd] overall_debt -36665
12/3/2009 7:11:10 PM Milkyway@home [wfd] overall_debt -92723
12/3/2009 7:11:10 PM SETI@home [wfd] overall_debt -36254
12/3/2009 7:11:10 PM World Community Grid [wfd] overall_debt 0
12/3/2009 7:11:10 PM [wfd] ------- end work fetch state -------
12/3/2009 7:11:10 PM World Community Grid [sched_op_debug] Starting scheduler request
12/3/2009 7:11:10 PM World Community Grid [wfd] request: 6480.00 sec CPU (6480.00 sec, 1)
12/3/2009 7:11:10 PM World Community Grid Sending scheduler request: To fetch work.
12/3/2009 7:11:10 PM World Community Grid Requesting new tasks
12/3/2009 7:11:10 PM World Community Grid [sched_op_debug] CPU work request: 6480.00 seconds; 1 idle CPUs
12/3/2009 7:11:20 PM World Community Grid Scheduler request completed: got 1 new tasks
12/3/2009 7:11:20 PM World Community Grid [sched_op_debug] Server version 601
12/3/2009 7:11:20 PM World Community Grid Project requested delay of 11 seconds
12/3/2009 7:11:20 PM World Community Grid [sched_op_debug] estimated total CPU job duration: 21963 seconds
12/3/2009 7:11:20 PM World Community Grid [sched_op_debug] Deferring communication for 11 sec
12/3/2009 7:11:20 PM World Community Grid [sched_op_debug] Reason: requested by project
12/3/2009 7:11:20 PM [work_fetch_debug] Request work fetch: RPC complete
12/3/2009 7:11:22 PM World Community Grid Started download of 26eee95b9d1510a8328474479188a66b.dat
12/3/2009 7:11:22 PM World Community Grid Started download of 316f3c66d8cbd517e67c5abf1465e233.dat
12/3/2009 7:11:23 PM World Community Grid Finished download of 26eee95b9d1510a8328474479188a66b.dat
12/3/2009 7:11:23 PM World Community Grid Finished download of 316f3c66d8cbd517e67c5abf1465e233.dat
12/3/2009 7:11:23 PM World Community Grid Started download of 2bd37a4f3ccb013743ef1d172535e1aa.pdb.gzb
12/3/2009 7:11:23 PM World Community Grid Started download of 7be5ac2c2f785d09078168f05f4f8072.pdb.gzb
12/3/2009 7:11:24 PM World Community Grid Finished download of 2bd37a4f3ccb013743ef1d172535e1aa.pdb.gzb
12/3/2009 7:11:24 PM World Community Grid Finished download of 7be5ac2c2f785d09078168f05f4f8072.pdb.gzb
12/3/2009 7:11:24 PM World Community Grid Started download of fcc8b6384c573a65b667968f4a7026d9.dat.gzb
12/3/2009 7:11:25 PM World Community Grid Finished download of fcc8b6384c573a65b667968f4a7026d9.dat.gzb
12/3/2009 7:11:25 PM rosetta@home [debt] CPU debt -14556.43 delta 17.59 share frac 0.13 (100.00/800.00) secs 140.76 rsc_secs 0.00
12/3/2009 7:11:25 PM Leiden Classical [debt] CPU debt -12897.77 delta -22.62 share frac 0.13 (100.00/800.00) secs 140.76 rsc_secs 40.22
12/3/2009 7:11:25 PM Docking@Home [debt] CPU debt -13398.83 delta -2.51 share frac 0.13 (100.00/800.00) secs 140.76 rsc_secs 20.11
12/3/2009 7:11:25 PM Einstein@Home [debt] CPU debt -36647.71 delta 17.59 share frac 0.13 (100.00/800.00) secs 140.76 rsc_secs 0.00
12/3/2009 7:11:25 PM Milkyway@home [debt] CPU debt -92705.64 delta 17.59 share frac 0.13 (100.00/800.00) secs 140.76 rsc_secs 0.00
12/3/2009 7:11:25 PM SETI@home [debt] CPU debt -36236.70 delta 17.59 share frac 0.13 (100.00/800.00) secs 140.76 rsc_secs 0.00
12/3/2009 7:11:25 PM World Community Grid [debt] CPU debt -45.24 delta -45.24 share frac 0.25 (200.00/800.00) secs 140.76 rsc_secs 80.43
12/3/2009 7:11:25 PM [debt] CPU debt: adding offset 45.24
12/3/2009 7:11:25 PM World Community Grid Starting CMD2_0182-ANXA7A.clustersOccur-1RA6_A.clustersOccur_28_0
12/3/2009 7:11:26 PM World Community Grid Starting task CMD2_0182-ANXA7A.clustersOccur-1RA6_A.clustersOccur_28_0 using hcmd2 version 614
12/3/2009 7:11:26 PM Leiden Classical chosen: CPU major shortfall
12/3/2009 7:11:26 PM [wfd] ------- start work fetch state -------
12/3/2009 7:11:26 PM [wfd] target work buffer: 17280.00 + 8640.00 sec
12/3/2009 7:11:26 PM [wfd] CPU: shortfall 60972.54 nidle 0.00 saturated 4210.97 busy 0.00 RS fetchable 600.00 runnable 400.00
12/3/2009 7:11:26 PM rosetta@home [wfd] CPU: fetch share 0.17 debt -14511.18 backoff dt 0.00 int 0.00
12/3/2009 7:11:26 PM Leiden Classical [wfd] CPU: fetch share 0.17 debt -12852.52 backoff dt 0.00 int 0.00
12/3/2009 7:11:26 PM Docking@Home [wfd] CPU: fetch share 0.17 debt -13353.59 backoff dt 0.00 int 0.00
12/3/2009 7:11:26 PM Einstein@Home [wfd] CPU: fetch share 0.17 debt -36602.47 backoff dt 0.00 int 0.00
12/3/2009 7:11:26 PM Milkyway@home [wfd] CPU: fetch share 0.17 debt -92660.39 backoff dt 0.00 int 0.00 (overworked)
12/3/2009 7:11:26 PM SETI@home [wfd] CPU: fetch share 0.17 debt -36191.46 backoff dt 0.00 int 0.00
12/3/2009 7:11:26 PM World Community Grid [wfd] CPU: fetch share 0.00 debt 0.00 backoff dt 0.00 int 0.00 (comm deferred)
12/3/2009 7:11:26 PM rosetta@home [wfd] overall_debt -14511
12/3/2009 7:11:26 PM Leiden Classical [wfd] overall_debt -12853
12/3/2009 7:11:26 PM Docking@Home [wfd] overall_debt -13354
12/3/2009 7:11:26 PM Einstein@Home [wfd] overall_debt -36602
12/3/2009 7:11:26 PM Milkyway@home [wfd] overall_debt -92660
12/3/2009 7:11:26 PM SETI@home [wfd] overall_debt -36191
12/3/2009 7:11:26 PM World Community Grid [wfd] overall_debt 0
12/3/2009 7:11:26 PM [wfd] ------- end work fetch state -------
12/3/2009 7:11:26 PM Leiden Classical [sched_op_debug] Starting scheduler request
12/3/2009 7:11:26 PM Leiden Classical [wfd] request: 4320.00 sec CPU (4320.00 sec, 0)
12/3/2009 7:11:26 PM Leiden Classical Sending scheduler request: To fetch work.
12/3/2009 7:11:26 PM Leiden Classical Requesting new tasks
12/3/2009 7:11:26 PM Leiden Classical [sched_op_debug] CPU work request: 4320.00 seconds; 0 idle CPUs
12/3/2009 7:11:31 PM Leiden Classical Scheduler request completed: got 1 new tasks
12/3/2009 7:11:31 PM Leiden Classical [sched_op_debug] Server version 510
12/3/2009 7:11:31 PM Leiden Classical Project requested delay of 182 seconds
12/3/2009 7:11:31 PM Leiden Classical [sched_op_debug] estimated total CPU job duration: 6999 seconds
12/3/2009 7:11:31 PM Leiden Classical [sched_op_debug] Deferring communication for 3 min 1 sec
12/3/2009 7:11:31 PM Leiden Classical [sched_op_debug] Reason: requested by project
12/3/2009 7:11:31 PM [work_fetch_debug] Request work fetch: RPC complete
12/3/2009 7:11:32 PM [work_fetch_debug] Request work fetch: Backoff ended for World Community Grid
12/3/2009 7:11:32 PM rosetta@home [debt] CPU debt -14504.52 delta 6.66 share frac 0.13 (100.00/800.00) secs 53.29 rsc_secs 0.00
12/3/2009 7:11:32 PM Leiden Classical [debt] CPU debt -12859.19 delta -6.66 share frac 0.13 (100.00/800.00) secs 53.29 rsc_secs 13.32
12/3/2009 7:11:32 PM Docking@Home [debt] CPU debt -13353.59 delta 0.00 share frac 0.13 (100.00/800.00) secs 53.29 rsc_secs 6.66
12/3/2009 7:11:32 PM Einstein@Home [debt] CPU debt -36595.80 delta 6.66 share frac 0.13 (100.00/800.00) secs 53.29 rsc_secs 0.00
12/3/2009 7:11:32 PM Milkyway@home [debt] CPU debt -92653.73 delta 6.66 share frac 0.13 (100.00/800.00) secs 53.29 rsc_secs 0.00
12/3/2009 7:11:32 PM SETI@home [debt] CPU debt -36184.80 delta 6.66 share frac 0.13 (100.00/800.00) secs 53.29 rsc_secs 0.00
12/3/2009 7:11:32 PM World Community Grid [debt] CPU debt -19.98 delta -19.98 share frac 0.25 (200.00/800.00) secs 53.29 rsc_secs 33.31
12/3/2009 7:11:32 PM [debt] CPU debt: adding offset 19.98
12/3/2009 7:11:33 PM Leiden Classical Started download of classical.butane_molecule_BIG_164284800_1259566726_5364
12/3/2009 7:11:34 PM Leiden Classical Finished download of classical.butane_molecule_BIG_164284800_1259566726_5364
12/3/2009 7:11:34 PM rosetta@home [debt] CPU debt -14482.49 delta 2.04 share frac 0.13 (100.00/800.00) secs 16.35 rsc_secs 0.00
12/3/2009 7:11:34 PM Leiden Classical [debt] CPU debt -12841.25 delta -2.04 share frac 0.13 (100.00/800.00) secs 16.35 rsc_secs 4.09
12/3/2009 7:11:34 PM Docking@Home [debt] CPU debt -13333.61 delta 0.00 share frac 0.13 (100.00/800.00) secs 16.35 rsc_secs 2.04
12/3/2009 7:11:34 PM Einstein@Home [debt] CPU debt -36573.78 delta 2.04 share frac 0.13 (100.00/800.00) secs 16.35 rsc_secs 0.00
12/3/2009 7:11:34 PM Milkyway@home [debt] CPU debt -92631.71 delta 2.04 share frac 0.13 (100.00/800.00) secs 16.35 rsc_secs 0.00
12/3/2009 7:11:34 PM SETI@home [debt] CPU debt -36162.77 delta 2.04 share frac 0.13 (100.00/800.00) secs 16.35 rsc_secs 0.00
12/3/2009 7:11:34 PM World Community Grid [debt] CPU debt -6.13 delta -6.13 share frac 0.25 (200.00/800.00) secs 16.35 rsc_secs 10.22
12/3/2009 7:11:34 PM [debt] CPU debt: adding offset 6.13

---

http://sciencesprings.wordpress.com
http://facebook.com/sciencesprings

12/3/2009 7:11:10 PM World Community Grid Sending scheduler request: To fetch work.
12/3/2009 7:11:10 PM World Community Grid Requesting new tasks
12/3/2009 7:11:10 PM World Community Grid [sched_op_debug] CPU work request: 6480.00 seconds; 1 idle CPUs
12/3/2009 7:11:20 PM World Community Grid Scheduler request completed: got 1 new tasks
12/3/2009 7:11:20 PM World Community Grid [sched_op_debug] Server version 601
12/3/2009 7:11:20 PM World Community Grid Project requested delay of 11 seconds
12/3/2009 7:11:20 PM World Community Grid [sched_op_debug] estimated total CPU job duration: 21963 seconds
12/3/2009 7:11:20 PM World Community Grid [sched_op_debug] Deferring communication for 11 sec
12/3/2009 7:11:20 PM World Community Grid [sched_op_debug] Reason: requested by project
12/3/2009 7:11:20 PM [work_fetch_debug] Request work fetch: RPC complete

See? You have work for WCG now. Slightly more than you bargained for as well, ~22,000 seconds instead of 6480 seconds. That's just because their tasks aren't any smaller, so you get what they have, even if you don't ask for that much.

I also see:

12/3/2009 7:11:10 PM [wfd] target work buffer: 17280.00 + 8640.00 sec

This coincides nicely with your Connect to of 0.2 and Additional buffer of 0.l days. 0.2 days = 4.8 hours = 17280 seconds. 0.1 days = 2.4 hours = 8640 seconds.

And seeing:

12/3/2009 7:11:26 PM Docking@Home [wfd] CPU: fetch share 0.17 debt -13353.59 backoff dt 0.00 int 0.00

If it's allowed to fetch work and it has work, Docking will fetch work next. It has the lowest debt.

---

Jord-

Thanks so very much for coming to my aid. So, now, should I leave the Connect at .2 and the Additional at .1? Is this sufficient to yield enough LTD? I don't know if the LTD is based on the sum of .2 +.1 = 207360 or just the .2 = 138240.

I think from what you said, "...By setting Run Always and Network activity always available, you override any preferences you set on them. So you override the Connect to of 0.20.

The Additional Buffer isn't overridden as it's got nothing to do with the actual Run or Connect preferences, only with how much cache you want to hold...." that it would be the .2 = 138240.

And I do not know which is preferred, the Connect = .2 and Additional =.1 with Activity based on the prefs; or Connect = 0.00 and Additional = 0.00 and Activity on Always.

Thanks.

---

http://sciencesprings.wordpress.com
http://facebook.com/sciencesprings

With the Connect to you tell BOINC at what time intervals it should contact the projects for uploading, reporting and downloading. So in your case, if you just had contact with a server and some work became ready to upload or report after that, BOINC will wait 4.8 hours (4h 48m) before making contact.

It doesn't tell how much cache you want. Only the additional buffer option will do that. And that's quite easily checked, by setting Connect to to 0.2, Additional buffer to 0.0000 (just zero).

BOINC will then request 1 (one) second of work from whichever project is eligible to ask for work next.

You will have to change that in your local preferences as you're using those.

12/3/2009 7:09:07 PM Reading preferences override file

These will override the web-preferences for the same settings.

**
I just set my additional work to zero seconds and did an update on a project. It'll ask for work for my GPU at that time, but it shows what you'll see if you do that:
04-Dec-09 02:00:57 Milkyway@home update requested by user
04-Dec-09 02:00:59 Milkyway@home [sched_op_debug] Starting scheduler request
04-Dec-09 02:00:59 Milkyway@home Sending scheduler request: Requested by user.
04-Dec-09 02:00:59 Milkyway@home Requesting new tasks for GPU
04-Dec-09 02:00:59 Milkyway@home [sched_op_debug] CPU work request: 0.00 seconds; 0 idle CPUs
04-Dec-09 02:00:59 Milkyway@home [sched_op_debug] ATI GPU work request: 1.00 seconds; 1 idle GPUs
**

---

Thanks.

Here is the conundrum. With the way this i7-920 is going through WU's, finishing most things in less than three hours, it looks to me like I do not want to wait 4.8 hours for new contact with the server(s). It sounds like I should either set Connect to .10 leaving the Activity based on prefs; or 0.00 and then switch activity to Always. If I set Connect to .1,I lower the figure for LTD to 69120. So I think that means, if I understand it at all, that any project that gets to x = <-69120, if it is possible, will not get any work.

Do I have any of this right?

I feel the need to interject here, there are a lot of people like me who can afford to go out and buy a pretty darned powerful and fast machine. I mean, you know not dual Xeons, just that normal machines these days are really fast, 64 bit, quad or hyper-threaded quads, and the projects running BOINC need these people if this work is to grow. Nothing that I am doing is unique. Most of the people who will be coming to projects now will be as ignorant as I am. The BOINC software - and WCG for that matter - have been around now long enough that projects have attracted the greatest portion of technically proficient people who can afford to just let their machines run on and on. It is clearly not any longer just install BOINC and some projects and stay with the defaults. My two Core 2 Duo Vista machines have never been moved from the original defaults of any build I use and they just crunch merrily along. But, they are ancient at three years old. Especially with Win 7 64bit and the I7 processors, it is a brand new day.

So, everything addressed here will hopefully be of use to others who come to these forums looking for help and searching through threads.

I would just now like to know if you think that I should stay at .2, or drop to .1, and stay with prefs in Activity; or drop to 0.00 and switch Activity to Always.

Thanks again for your patience.

---

http://sciencesprings.wordpress.com
http://facebook.com/sciencesprings

The connect to option is there primarily if you're on office LAN, 56k/ISDN modem or you're on one of those DSL packages that still charge you for every byte you get in/throw out.

If you have an always on internet connection, set the Connect to to zero.

To be quite frank, I don't really care about whether or not the long term debt is correct in choosing work for the correct project or not on any of my own machines. I (sometimes) read the (long and twisted) discussions about it on the development email list, but to know the complete insides and outsides of it? I truly don't know, as I am less than interested in that. ;-)

So sorry, I cannot help you there.

As for your Core Duos being ancient... I run a P4 3.0GHz and an AMD XP 2200+ ... if you ever want to get rid of one or both of those machines, let me know. I'll want them. :-)

P.S: it is 3am here, I am now off to bed for a couple of hours of shut-eye. Just in case you find I have gone silent, don't think I am ignoring you. Well, i am, but just for the time I sleep. :-)

---

Thanks so much. Good night, sleep tight....

---

http://sciencesprings.wordpress.com
http://facebook.com/sciencesprings

That's easily done... I'll ask those who know.

It's a couple more options anyway.
<client_version_check_url>
<client_download_url>
<network_test_url>
<proxy_test_server>
<version_check_server>

So email sent to Rom and Kevin. I'll let you know what they post back.

---

@Sekerob,

<proxy_test_server>
<version_check_server>

These two aren't used by the BOINC client, only by the WCG client.
Although even <version_check_server> isn't used by the newer WCG clients. They are using the <client_version_check_url> flag now as well.

All other flags are used by both clients. I have adapted my FAQ on that now, especially so since you are pointing to it from the WCG forum FAQs. :-)

---