I thought when the 'received' timestamp was introduced (http://boinc.berkeley.edu/trac/changeset/18531), it was only intended to influence the running order of GPU tasks?
Maybe it should be extended to schedule intra-project CPU tasks as well, leaving inter-project scheduling to debt (which GPU scheduling doesn't use at all). ----- Original Message ----- From: <[email protected]> To: "BOINC Alpha Mailing List" <[email protected]>; <[email protected]> Sent: Friday, August 14, 2009 3:17 PM Subject: [boinc_dev] 6.6.38 result sort order problem. > > The computer in question has 2 CPUs, and no GPUs. > > The problem is that I have 2 CPDN tasks, and after a restart, it insists > on > starting the task that was downloaded more recently if only one CPDN task > is started. The received_time for both was 0, but even after I changed > the > received_time for the newer one to be greater than 0, the newer one was > still favored for start over the older one. > > Another, but similar problem is that all results that are dowloaded in one > one batch get the same timestamp. I have 3 tasks from Virtual Prarie on > that machine with identical non-zero timestamps. It might have been > better > if we used a counter rather than a timestamp for this case. > > jm7 > > _______________________________________________ > 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.
