Not sure what you're asking; the only way to update the estimates
is to run more jobs with each version,
which I just checked in a change to do.
-- David
On 08-Dec-2010 4:04 PM, Richard Haselgrove wrote:
> Sure, host_app_versions.php lets the user know what the server currently
> believes to be th
Sure, host_app_versions.php lets the user know what the server currently
believes to be the situation.
But my question was more directed to finding out what the actual current
performance would be, with either or both applications - just in case the
server assessment had become disconnected fro
On 08-Dec-2010 12:21 PM, Richard Haselgrove wrote:
> Now that SETI is back up, details have emerged of a host where the records
> appear to indicate that v6.08 (plan_class cuda) is faster than v6.09
> (cuda23). At SETI, this would be unusual - cuda23 is usually significantly
> faster than cuda, e
David Anderson wrote, On 12/8/10 6:28 PM:
> 1) plan class is purely a server mechanism;
> it's relevant to all client versions.
> If an app_plan function references info that's only
> reported by certain clients (e.g., GPU list or CPU capabilities)
> then it will return false (i.e. that app versio
http://boinc.berkeley.edu/trac/wiki/PrefsRemodel
This isn't something we're going to do anytime soon,
but we may as well discuss it.
-- David
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
1) plan class is purely a server mechanism;
it's relevant to all client versions.
If an app_plan function references info that's only
reported by certain clients (e.g., GPU list or CPU capabilities)
then it will return false (i.e. that app version won't be sent).
2) clients report all the platform
Hi!
1. I'm not fully aware of how the client interacts with the scheduler
regarding plan classes. I'd need to send different Apps to clients that
do support plan classes (>= 6.2?) and those which don't. How do I do
this? Will a "generic" plan class (that doesn't actually e.g. check the
CPU ca
I checked in a fix.
-- David
On 08-Dec-2010 5:41 AM, john.mcl...@sybase.com wrote:
>
> I have another task at 100% with no time remaining that was due yesterday
> that is not running because another task on the same computer is running
> high priority. The task that is late is superlinkattechnion
Unfortunately, "close" to completion can be quite a long time for some
projects. For example, the last 5% of a CPDN task can take a couple of
weeks on some machines. We have discussed it in the past, and cannot come
up with any definition of "close" that is not completely open ended. In
the curr
I have regularly been seeing Docking WUs suspend at 100% completion. They
do eventually start running again and complete. It would be nice to keep
BOINC from pausing WUs close to completion if it's not too hard to do.
Regards/Ed
On Wed, Dec 8, 2010 at 7:51 AM, wrote:
> One bit of further inf
One bit of further information that might be useful. The superlink task
was reading as 253.xx% complete.
jm7
Sent by:
I have another task at 100% with no time remaining that was due yesterday
that is not running because another task on the same computer is running
high priority. The task that is late is superlinkattechnion
superlink_wu_04_12_2010_06_2310751429726814_8408_0. The task that is
running is primaboin
12 matches
Mail list logo
