viewing queued work with GAH client preference?

Michael_qrt · Post by **Michael_qrt** » Tue May 25, 2004 2:06 am

Since I have recently been having some problems with the HTTP proxy server here at uni, my main folder has been rather inactive over the last few days. So I decided to change the settings to allow my machine to queue up work units. As someone mentioned here you can do this by changing the client preference to G@H and then setting batch down/uploads.

What I want to know is if anyone knows exactly how this works. I've looked at the logs and I can't tell if there is any work units queued up (I have verbosity 9). So is there a way to see what units are in the queue (if any)?

Also does the client wait till the queue is empty before uploading the results or does it try to upload as normal?

Thanks for any info you can give me about how this feature behaves.

Wrah · Post by **Wrah** » Tue May 25, 2004 2:26 pm

Ah, that would probably be me.

First of all, after you have set the preference to gah you have to stop and start the client to make it fill the queue. You will see clearly then in the log that it has downloaded 9 WU's. To view what is in the queue, simply start the (console) client with the command line option '-queueinfo'. (with the graphical client, simply right-click on the icon in the system tray and choose queueinfo or something in the menu)

I just filled up my queue so here's an example of what it looks like in the log:

Code: Select all

[22:23:24] - Ask before connecting: No
[22:23:24] - Genome@Home mode
[22:23:24] - User name: Wrah (Team 31574)
[22:23:24] - User ID = 71C8376567D4471E
[22:23:24] - Machine ID: 1
[22:23:24] 
[22:23:24] Loaded queue successfully.
[22:23:24] + Benchmarking ...
[22:23:26] The benchmark result is 7384
[22:23:26] - Autosending finished units...
[22:23:26] Trying to send all finished work units
[22:23:26] + No unsent completed units remaining.
[22:23:26] - Autosend completed
[22:23:29] - Preparing to get new work units...
[22:23:29] + Attempting to get work packet
[22:23:29] - Connecting to assignment server
[22:23:29] Connecting to http://assign.stanford.edu:8080/
[22:23:30] Initial: 43AB; - Successful: assigned to (171.67.89.100).
[22:23:30] + News from Genome@Home: Welcome to Folding@Home
[22:23:30] Loaded queue successfully.
[22:23:30] Connecting to http://171.67.89.100:8080/
[22:23:32] Initial: 0000; - Deadline time not received.
[22:23:32] - Receiving payload (expected size: 353471)
[22:23:35] - Downloaded at ~115 kB/s
[22:23:35] - Averaged speed for that direction ~219984 kB/s
[22:23:35] + Received work.
[22:23:35] + Attempting to get work packet
[22:23:35] - Connecting to assignment server
[22:23:35] Connecting to http://assign.stanford.edu:8080/
[22:23:36] Initial: 43AB; - Successful: assigned to (171.67.89.100).
[22:23:36] + News from Genome@Home: Welcome to Folding@Home
[22:23:36] Loaded queue successfully.
[22:23:36] Connecting to http://171.67.89.100:8080/
[22:23:37] Initial: 0000; - Deadline time not received.
[22:23:37] - Receiving payload (expected size: 353312)
[22:23:41] - Downloaded at ~86 kB/s
[22:23:41] - Averaged speed for that direction ~176004 kB/s
[22:23:41] + Received work.
[22:23:41] + Attempting to get work packet
[22:23:41] - Connecting to assignment server
[22:23:41] Connecting to http://assign.stanford.edu:8080/
[22:23:41] Initial: 43AB; - Successful: assigned to (171.67.89.100).
[22:23:41] + News from Genome@Home: Welcome to Folding@Home
[22:23:42] Loaded queue successfully.
[22:23:42] Connecting to http://171.67.89.100:8080/
[22:23:43] Initial: 0000; - Deadline time not received.
[22:23:43] - Receiving payload (expected size: 353435)
[22:23:46] - Downloaded at ~115 kB/s
[22:23:46] - Averaged speed for that direction ~140826 kB/s
[22:23:46] + Received work.
[22:23:46] + Attempting to get work packet
[22:23:46] - Connecting to assignment server
[22:23:46] Connecting to http://assign.stanford.edu:8080/
[22:23:47] Initial: 43AB; - Successful: assigned to (171.67.89.100).
[22:23:47] + News from Genome@Home: Welcome to Folding@Home
[22:23:47] Loaded queue successfully.
[22:23:47] Connecting to http://171.67.89.100:8080/
[22:23:48] Initial: 0000; - Deadline time not received.
[22:23:48] - Receiving payload (expected size: 355052)
[22:23:52] - Downloaded at ~86 kB/s
[22:23:52] - Averaged speed for that direction ~112678 kB/s
[22:23:52] + Received work.
[22:23:52] + Attempting to get work packet
[22:23:52] - Connecting to assignment server
[22:23:52] Connecting to http://assign.stanford.edu:8080/
[22:23:53] Initial: 43AB; - Successful: assigned to (171.67.89.100).
[22:23:53] + News from Genome@Home: Welcome to Folding@Home
[22:23:53] Loaded queue successfully.
[22:23:53] Connecting to http://171.67.89.100:8080/
[22:23:54] Initial: 0000; - Deadline time not received.
[22:23:54] - Receiving payload (expected size: 353922)
[22:23:57] - Downloaded at ~115 kB/s
[22:23:57] - Averaged speed for that direction ~90166 kB/s
[22:23:57] + Received work.
[22:23:57] + Attempting to get work packet
[22:23:57] - Connecting to assignment server
[22:23:57] Connecting to http://assign.stanford.edu:8080/
[22:23:58] Initial: 43AB; - Successful: assigned to (171.67.89.100).
[22:23:58] + News from Genome@Home: Welcome to Folding@Home
[22:23:58] Loaded queue successfully.
[22:23:58] Connecting to http://171.67.89.100:8080/
[22:24:00] Initial: 0000; - Deadline time not received.
[22:24:00] - Receiving payload (expected size: 352878)
[22:24:03] - Downloaded at ~114 kB/s
[22:24:03] - Averaged speed for that direction ~72155 kB/s
[22:24:03] + Received work.
[22:24:03] + Attempting to get work packet
[22:24:03] - Connecting to assignment server
[22:24:03] Connecting to http://assign.stanford.edu:8080/
[22:24:04] Initial: 43AB; - Successful: assigned to (171.67.89.100).
[22:24:04] + News from Genome@Home: Welcome to Folding@Home
[22:24:04] Loaded queue successfully.
[22:24:04] Connecting to http://171.67.89.100:8080/
[22:24:05] Initial: 0000; - Deadline time not received.
[22:24:05] - Receiving payload (expected size: 354853)
[22:24:08] - Downloaded at ~115 kB/s
[22:24:08] - Averaged speed for that direction ~57747 kB/s
[22:24:08] + Received work.
[22:24:08] + Attempting to get work packet
[22:24:08] - Connecting to assignment server
[22:24:08] Connecting to http://assign.stanford.edu:8080/
[22:24:09] Initial: 43AB; - Successful: assigned to (171.67.89.100).
[22:24:09] + News from Genome@Home: Welcome to Folding@Home
[22:24:09] Loaded queue successfully.
[22:24:09] Connecting to http://171.67.89.100:8080/
[22:24:11] Initial: 0000; - Deadline time not received.
[22:24:11] - Receiving payload (expected size: 354597)
[22:24:14] - Downloaded at ~115 kB/s
[22:24:14] - Averaged speed for that direction ~46221 kB/s
[22:24:14] + Received work.
[22:24:14] + Attempting to get work packet
[22:24:14] - Connecting to assignment server
[22:24:14] Connecting to http://assign.stanford.edu:8080/
[22:24:15] Initial: 43AB; - Successful: assigned to (171.67.89.100).
[22:24:15] + News from Genome@Home: Welcome to Folding@Home
[22:24:15] Loaded queue successfully.
[22:24:15] Connecting to http://171.67.89.100:8080/
[22:24:16] Initial: 0000; - Deadline time not received.
[22:24:16] - Receiving payload (expected size: 354445)
[22:24:19] - Downloaded at ~115 kB/s
[22:24:19] - Averaged speed for that direction ~37000 kB/s
[22:24:19] + Received work.
[22:24:19] Got 9 more work units.
[22:24:19] + Closed connections
[22:24:19] 
[22:24:19] + Processing work unit
[22:24:19] Core required: FahCore_65.exe
[22:24:19] Core found.
[22:24:19] Working on Unit 01 [May 25 22:24:19]
[22:24:19] + Working ...
...

And this is what the -queueinfo command shows:

Code: Select all

Arguments: -queueinfo 

[22:32:43] - Ask before connecting: No
[22:32:43] - Genome@Home mode
[22:32:43] - User name: Wrah (Team 31574)
[22:32:43] - User ID = 71C8376567D4471E
[22:32:43] - Machine ID: 1
[22:32:43] 
[22:32:43] Loaded queue successfully.
[22:32:43] Printing Queue Information
CURRENT QUEUE: 
00  READY     "Folding@Home" (78) 171.67.89.100:8080  May 25 22:24:19
01 *READY     "Folding@Home" (65) 171.64.122.143:8080  May 25 12:19:27 | July 1 12:19
02  READY     "Folding@Home" (78) 171.67.89.100:8080  May 25 22:23:35
03  READY     "Folding@Home" (78) 171.67.89.100:8080  May 25 22:23:41
04  READY     "Folding@Home" (78) 171.67.89.100:8080  May 25 22:23:46
05  READY     "Folding@Home" (78) 171.67.89.100:8080  May 25 22:23:52
06  READY     "Folding@Home" (78) 171.67.89.100:8080  May 25 22:23:57
07  READY     "Folding@Home" (78) 171.67.89.100:8080  May 25 22:24:03
08  READY     "Folding@Home" (78) 171.67.89.100:8080  May 25 22:24:08
09  READY     "Folding@Home" (78) 171.67.89.100:8080  May 25 22:24:14

Folding@home Client Shutdown.

The WU in slot #01 is the WU it was already working on. As you can see it came from a different server.
So now it has 10 WU's to work on before it needs an internet connection again. It will not upload a WU right after it has finished one. Instead it will try to upload finished WU's every 6 hours. It should also download new WU's again then to keep the queue filled, but for some reason it rarely does this and until now I have not found any logic in it.

Just stop and start the client once in a while, this will make it fill the queue again.

Michael_qrt · Post by **Michael_qrt** » Tue May 25, 2004 11:18 pm

Thanks for the info, it seems to be a little used or discussed feature of the FAH client.

Loking at my logs it seems as though there isn't any work queued up at the moment even after I stopped and restarted theclient a few times. I checked the settings and the batch option was set, so I don't know what's up with it.

I'll try again later and see if I can get soe work queued up.