To tell you the truth I was trying to keep it very simplistic, hence the "absolute" times. I figured that it would certainly be an improvement to what it does currently. Keeping track of how long things take is presumably a bit more complicated. Who knows it might help the guy on Seti who was complaining that he couldn't get his BM to respond. According to his computers list it had 11,084 tasks on board! Cheers, MarkJ ________________________________
Date: Tue, 9 Mar 2010 11:49:03 -0000 From: "Richard Haselgrove" <[email protected]> Subject: Re: [boinc_dev] DCF per app To: "TarotApprentice" <[email protected]>, "BOINC dev" <[email protected]> Message-ID: <797344650e15437a9c1183c85c23d...@anonymous> Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original 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! _______________________________________________ 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.
