At the moment I'm running GPUgrid on the GPU and World Community Grid on the CPU. My internet connection isn't very reliable, so I have the BOINC preferences set to "connect to the internet every 2 days" and work buffer 2 days also. And it works well with WCG, because I have about 30 "ready to start" tasks in the queue.

However, GPUgrid only ever has 2 tasks or so in the queue. With my GTX670, that's a maximum of 10 hours of work. So if my internet stops working for over 10 hours, the GPU ends up idle. Is there any way to tell GPUgrid to keep more tasks in reserve, but without getting any more WCG tasks added to the queue also?
____________

The max number of WUs GPUGrid allows per GPU is 2 at a time.
____________
Thanks - Steve

You mean regardless of my settings and the speed of my graphics card I will always have only one task on standby besides the one active task? Isn't there anything that can be done about this?

You mean regardless of my settings and the speed of my graphics card I will always have only one task on standby besides the one active task? Isn't there anything that can be done about this?

At the moment I'm running GPUgrid on the GPU and World Community Grid on the CPU. My internet connection isn't very reliable, so I have the BOINC preferences set to "connect to the internet every 2 days" and work buffer 2 days also. And it works well with WCG, because I have about 30 "ready to start" tasks in the queue.

Probably best to just select the long runs.

What's up with your Internet connection?

Probably best to just select the long runs.

What's up with your Internet connection?

I was wondering that too, until I saw the size of the file being uploaded.

67,644 KiB ??!!

The more you compress a file, the longer it takes to uncompress it. Could the server handle that workload?

If it's better than what is presently used by Boinc then it should replace what is being used by Boinc. Otherwise GPUGrid (and any other project) would have to bypass the Boinc compression system. Presumably the Boinc server would also have to be bypassed. The next server upgrade would represent the problem with any such bespoke compression implementation and it might cause cross-boinc compatibility issues.

I was wondering that too, until I saw the size of the file being uploaded.

67,644 KiB ??!!

probably about time to implement 7-zip compression of the results before upload.

You can try increase BOINCmanager "Minimum Work Buffer" ( 2 days ) and "Max Additional work buffer" ( 4 days ).

____________

Might be modem/router specific, so changing ISP could help, if they supplied the modem/router. Perhaps they are assigning an IP address for a very short time period or some TTL value is low. Have you tried keeping a web page open? One with meta refresh (msn, yahoo or even a streaming news station).

Might be useful if the project could adapt a trickle upload process, but I doubt that would be readily doable.

You can try increase BOINCmanager "Minimum Work Buffer" ( 2 days ) and "Max Additional work buffer" ( 4 days ).

It does not work increase min-max work buffer, the project limits the maximum send WUs to two per GPU at every given moment. As I have written before, it seems to me, the best solution would be to increase the WU limit to 4, as cude4.2 app are 30 to 40% or even more faster than cuda3.1 app on GPUGRID.

If project management would be able to reconsider this limitation, either increase WU limit or - although I do not know if this would be possible – increase the size of each Cuda4.2 WU, so it would be 8 to 12 hours processing time for each WU again. Although I am anxious of an upload file of let´s say 160 MB.

In my special case, after reconsidering, my internet connection should not be a problem, as I do have 512 kbytes/s upload-speed with a fix IP, but it seems that the GPUGRID server limits incoming results to a max speed of ca. 50 kbytes/s. And yes it loses connection several times on my side or project side?!