Hey, I've noticed the project down "under maintenance" lately - and my system runs out of units to process before the site goes online again.

Is there anyway I can increase the amount of cached units - my GPU processes them in like 9-10minutes per unit so I need a larger cache so the server doesnt process them all before the project is back online and sits idle for several hours.t94xr - Taupo, New Zealand. | cameronwalker.nz - server

Hi,
My Titan V does guppi vlars in 39-48 seconds. I run out of work in 1 h 20 mins with a 100 WU cache. Shorties take 17 seconds.To overcome Heisenbergs:
"You can't always get what you want / but if you try sometimes you just might find / you get what you need." -- Rolling Stones

There are many ways to solve this problem :
- you can modify the boinc code to remove this 100 wu limit (as Petri did)
- you can use an old boinc version which don't have such limitation (boinc 6.10.58 as kittyman do)
- you can use a script to fill the cache before the maintenance (as I do)

You can download my perl tool cpu2gpu.pl at http://www.w3perl.com/seti/
Hope it helps !

No. You can only bank 100 units for the CPU and 100 for each GPU that you might have.

So it will increase to 200 for my second GPU when that's installed. hmm thanks.

Hi,
My Titan V does guppi vlars in 39-48 seconds. I run out of work in 1 h 20 mins with a 100 WU cache. Shorties take 17 seconds.

You sir, I tip my hat. :)

There are many ways to solve this problem :
- you can modify the boinc code to remove this 100 wu limit (as Petri did)
- you can use an old boinc version which don't have such limitation (boinc 6.10.58 as kittyman do)
- you can use a script to fill the cache before the maintenance (as I do)
...

That's an excellent idea - find the 100 limit in the code.
I'll do some investigation about this.t94xr - Taupo, New Zealand. | cameronwalker.nz - server

Server side code still hard limits the number of tasks in your cache to 100 per device per scheduler work request. The other limitation is in the client side code that limits the number of tasks being held on any host to 1000 tasks for BOINC versions >> 7.2.0 when bunkering via rescheduling is being used.

Earlier BOINC versions like the 6.10.58/60 mentioned or modified client code allows up to 3000 tasks to be held per host. "Bunkering" or rescheduling is the only way to have enough tasks to make it through our typical 10-12 hour maintenance period.Seti@Home classic workunits:20,676 CPU time:74,226 hours

There are many ways to solve this problem :
- you can modify the boinc code to remove this 100 wu limit (as Petri did)
- you can use an old boinc version which don't have such limitation (boinc 6.10.58 as kittyman do)
- you can use a script to fill the cache before the maintenance (as I do)

You can download my perl tool cpu2gpu.pl at http://www.w3perl.com/seti/
Hope it helps !

This should work on a Mac right? I don’t know if the folder structure is the same before Linux and a Mac.

Doesn't matter. The Perl script has a line where you input the BOINC folder location on your system. You just have to adjust Laurent's script, comment out some superfluous lines and uncomment another line to make the task move at the end of the script. You do have to install some version of Perl for your OS as a starter.
[Edit] You might want to begin here to learn the genesis of the various Reschedulers.GUPPI Rescheduler for Linux and Windows - Move GUPPI work to CPU and non-GUPPI to GPUSeti@Home classic workunits:20,676 CPU time:74,226 hours

Thanks and sure, I used the rescheduler someone made on here years ago on Windows. I just hadn’t seen a fairly clean/easy option for the Mac. I installed Perl earlier today. I’ll give the script a look and see how it goes. The 1080ti is very thirsty on maintenance days...lol

I'm with you Mark, a few are (fairly) responsible with their efforts to break the server limits on how many tasks they hoard, while others may be somewhat less so. All who do so forget that SETI has NEVER promised us full caches all the time.Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?