| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: Project changing - cache settings from old project at first server connect? |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 4
|
|
| Author |
|
|
Mathilde2006
Senior Cruncher Germany Joined: Sep 30, 2006 Post Count: 269 Status: Offline Project Badges: 
|
Hi,
----------------------------------------I have my client set to the HST project-settings: Connect to network about every 0.1 days Cache 6.0 extra days of work. I moved two clients to MCM- settings: Connect to network about every 0.1 days Cache 1.5 extra days of work. In the project tab I clicked the refresh button and now I got on each client around 20 new MCM WUs- one of the quad core clients need ~ 19hours for an MCM WU and the other one around 24 hours. So I assume, that the client did move to the new project, but still has had the cache settings from the 'old' project at that time. Boinc client 7.6.22 on Windows 10 32bit. If it is made by design- the workaround would be- stay in the old project- adjust the cache setitings here to the level of the new project- click refresh in the project tab, move the client to the new project with(out) pressing the refresh button. Didn't find this feature in the FAQ. Well -the surprising WU rain should take me to the 10 year MCM badge.   [Edit 1 times, last edit by Mathilde2006 at Aug 18, 2016 7:57:55 AM] |
||
|
|
SekeRob
Master Cruncher Joined: Jan 7, 2013 Post Count: 2741 Status: Offline |
Before new profile settings take effect they have to transmit first, so changing cache and project selections at same time, will on first update do work request at 'on client' known old settings. Connect with the developers [alpha mail list] to make a case of changing that order... as presently the client tells on connect:
----------------------------------------1) What does the client want: work of course. 2) Is there a profile update and if so push it to client. Combined in a single scheduler connect. The server has no way of knowing if local preferences are in effect as override, so the first scheduler request always transmits the 'effective' settings from the client with the number of seconds work the active buffer has shortfall for... getting work to the client being first priority. [Edit 2 times, last edit by SekeRob* at Aug 18, 2016 8:27:51 AM] |
||
|
|
SekeRob
Master Cruncher Joined: Jan 7, 2013 Post Count: 2741 Status: Offline |
Additional buffer is a fairly useless function as the WCG projects have low caps on the number of WU provided per request. As soon as the buffered work is over minimum setting, the additional buffer part is ignored.
|
||
|
|
Mathilde2006
Senior Cruncher Germany Joined: Sep 30, 2006 Post Count: 269 Status: Offline Project Badges:
|
Thanks- next time I press the 'no new tasks' button before the refresh.
----------------------------------------I only have a big HT cache, because I have an estimated time frame of around 40 hours per WU on some PCs. Run time is 8 hours. That are 1.5 'real' days- the same as I have running with MCM. |
||
|
|
|