To be precise, up to 120, u get 10 at the time. If u have set a large buffer like your proposed 5.5 days, BOINC should automatically take care of fetching u more work, but it will send them in sets of 10. What it does after the first 10 is compute how much time your particular machine would take to complete the work according the benchmark and a few other 'performance' criteria that BOINC maintains locally. If it than determines that your buffer is not filled up, BOINC would request more.

120 is a protection rule. To get more in a day u would have to send a mail.

why you are not getting more in your buffer than 10-12 WU's has very much to do with the actual work.

If after letting BOINC alone for a few days, nothing is improving while staying permanently connected, it could be that some values have somehow gotten inflated like the Duration Correction Factor (DCF). Than it's suggested to set the option 'do not fetch new work', work off the tasks in the tasks buffer and than do a Reset in the projects tab.

How many seconds of work is being requested? You should see that in the message tab right before a download starts. If it's a very low value or a highly inflated value like millions of seconds, the mention reset is the path to follow.

Oh, and i do hope you dont have created a general_prefs_override.xml file. U can change anything in the web profile, but if a work buffer value is in that file, it will supersede. U'd have to change the override file and force BOINC to read the prefs again thru the Update option.

long winded, but hope there is an answer somewhere in here.

PS1 Normally if you buffer 5.5 days, u are not, by logic expected to be connected for that period. U can though schedule a daily connect of e.g. 1 hour..... that should be enough to send back results and fetch new work to back fill the buffer.

PS2 The 5.8 version has a manual 5 minute override feature. Even if u told BOINC to 'connect per schedule', if u hit update, it will do its upload/download thing for 5 minutes or for as long as upload/download is ongoing (i think, but never observed). Same goes for disconnecting. It will stay an extra 5 minutes connected.

cheers

Cio, that message is standard ..... BOINC has a mind of it's own. Often 10 minutes later it starts pulling work, if it sees room in the buffer. Some of the design is to make it the least burdensome on the servers and there are multiple, that perform different tasks in a BOINC environment.

cheers

What operating system? It would make a difference in the BOINC version we're talking about.

I tried running either an alpha or beta 5.7 BOINC version on Windows and could never get more than ten workunits at a time. They would run completely down to nothing before sending 10 more, regardless of the number of days set in the network field.

I reverted to the production 5.4.11 BOINC version and the queue happily filled up to where I had set it. When one or a few workunits complete, more work comes in when I am connected.

Do the profiles all have the same "Connect to server every X days" value? It sounds like the Work profile has the 0.1 default value.

I have the same situation as retsof's. I had already finished resetting the project and it's still the same-I couldn't download anything more than ten WUs at a time. The computer has to finish crunching the ten WUs before downloading another batch of 10 WUs.

I'm running BOINC 5.8.2 for Windows and my DCF is 0.926484. I guess Sekerob and retsof are both right, the particular version of BOINC running in the computer has something to do with it.

Should I go back to 5.4.11?