I did raise a Trak ticket for this quite some time back but it was put into the "too hard" basket. I would add that most projects seem to have multiple apps these days, examples apart from yours are Seti, Einstein, GPUgrid and ClimatePrediction to name a few more. Perhaps we could take another look at it again please. Cheers, MarkJ ________________________________
Date: Sun, 7 Mar 2010 18:43:36 +0200 From: Rytis Slatkevi?ius <[email protected]> Subject: [boinc_dev] DCF per app To: BOINC Developers Mailing List <[email protected]> Message-ID: <[email protected]> Content-Type: text/plain; charset=UTF-8 I am going to raise DCF per app question once again. PrimeGrid currently has 13 different applications with varying task durations and optimization levels for different CPUs. Also available are GPU apps. This makes it very hard to correctly estimate the duration of tasks, and it throws BOINC duration estimate very much off when you run more than one application type. For example if you ran an app which was overestimated and had short tasks, and then switched to an app which has long tasks that are overestimated, it would make it seem that they will run for months, which leads to user complaints and lost CPU time because of WUs being cancelled, sometimes with a few days of progress. This has become a number one problem being discussed in the PG forums. Therefore I'm going to ask to once again reconsider implementing DCF per app instead of having it per project only. -- Pagarbiai / Sincerely Rytis Slatkevi?ius _______________________________________________ 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.
