It's fun to say "oh, that was August 2009" but programming is hard to schedule.
Seriously. The first hardware engineer to go over budget was Charles Babbage, and the first programmer to miss schedules was Agusta Ada King, Countess of Lovelace. Feel free to look it up. We can talk about the scheduled completion time, but not the actual time. As the note points out, the server has to know this, that means an extension to the client to server protocol, and the schedulers on both sides have to understand it. -- Lynn On 3/8/2010 12:00 AM, TarotApprentice wrote: > As you point out Dave said on the ticket "End of August" (2009). We are well > past that now. Perhaps it can get bumped up the priority list. It might also > solve some of the over/under work fetch issues people have been having. For > those that are interested Jord has put a link to it below. > > Thanks > MarkJ > > > > ________________________________ > From: Jorden van der Elst<[email protected]> > To: TarotApprentice<[email protected]> > Cc: [email protected] > Sent: Mon, 8 March, 2010 5:31:42 PM > Subject: Re: [boinc_dev] DCF per app > > It wasn't put into the "too hard" basket. It was put into the "end of > August **or so**" basket. > > http://boinc.berkeley.edu/trac/ticket/812#comment:3 > "Maintaining per-app-version DCF in the client isn't too hard, but > that's only part of the job; DCF is also used by the scheduler to > decide what jobs can be sent. For this, we'd also need to add to > scheduler requests a list of app versions and their DCFs, and extend > the scheduler to parse this and use the DCFs if present. I won't have > time to do this until late Aug. or so. " > > On Mon, Mar 8, 2010 at 7:25 AM, TarotApprentice > <[email protected]> wrote: >> 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. >> > > > _______________________________________________ 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.
