This may be an over-simplistic suggestion - but why not keep track of how 
long the *last* RPC took, and don't start another one until both the RPC 
itself, and all necessary post-processing (sorting, display updating) have 
completed?

Putting absolute values in would be a bad idea - there'll always be somebody 
around with an Atom CPU and four GTX 295 CUDA cards to break it!


> Jord and I were discussing a message thread on Seti where some of the 
> users are complaining. One of the points raised was the "communicating 
> with boinc client" messages which occur when people have large numbers of 
> tasks on hand. Jord has provided a link to one of his replies regarding 
> this issue with a registry patch in case people have turned the "show 
> active tasks" filter off and need to get it back on. Thanks Jord.

> I'd like to suggest that we decrease the frequency that we refresh the 
> task list when there are large numbers of tasks on the machine. I believe 
> its currently set to refresh at 1 second. Say 1.5 seconds when we have 
> 1500+ tasks, Increase to 2 secs when we have 3000+ tasks, 2.5 secs for 
> 4500+ tasks and maybe 3 secs on 6000+ tasks and so on. I don't know if its 
> feasable for half seconds, so if not then use the 1 second increments. I 
> wouldn't go past about 3 seconds as that would appear to not refresh 
> frequently enough. It might just save the manager hammering the client for 
> RPC requests.

> Cheers,
MarkJ

________________________________


> 2. "Communicating with boinc client" messages

People shouldn't be trying to look at 4,000 tasks in their manager.
The fix for that is to use the "Show active tasks" button and if they
cannot get that to work since they stupidly clicked the button so it
**shows** "Show active tasks", they'll have to edit their registry as
I detailed here:
http://setiathome.berkeley.edu/forum_thread.php?id=58980&nowrap=true#975902

That post also shows why BM just cannot do that. Linear or not. :-)




_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.


_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Reply via email to