Opened 14 years ago

Last modified 10 years ago

#994 reopened Defect

BOINC Benchmark

Reported by: rebirther Owned by: davea
Priority: Undetermined Milestone: Undetermined
Component: Client - Daemon Version: 6.11.7
Keywords: benchmark Cc: peter.b.slacik@…

Description

It is not necessary to run the benchmark every 5 days in a running BOINC. Its better to run it every a five days count only if you restart BOINC or as now every new version.

Change History (4)

comment:1 Changed 14 years ago by Christian Beer

Component: UndeterminedClient - Daemon
Keywords: benchmark added
Owner: set to davea

comment:2 Changed 14 years ago by davea

Resolution: fixed
Status: newclosed

(In [22365]) - client: if we successfully did CPU benchmarks,

don't keep doing them every 5 days unless restart the client fixes #994

comment:3 in reply to:  2 Changed 14 years ago by Pepo

Cc: peter.b.slacik@… added
Resolution: fixed
Status: closedreopened
Type: EnhancementDefect
Version: 6.10.566.11.7

Replying to davea:

...if we successfully did CPU benchmarks, don't keep doing them every 5 days unless restart the client...


But as rebirther noted:

...only if you restart BOINC or as now every new version.

Today I've updated 6.11.7 -> 6.11.8 (Win7, compatibility install). In a few seconds after automatic post-install-start I've noticed, that the Mgr+client are running under admin's account, so I've stopped them (just during an unfinished benchmark). After new start (under the intended plain-user account), the new client did not do benchmarks at all.

What about machines (like notebooks, etc), which speed (CPU frequency) does vary with time and temperature and else, while the client might be running uninterrupted for weeks?

comment:4 Changed 10 years ago by Richard Haselgrove

The code in [22365] - now 2985faec - doesn't prevent an automatic benchmark being run under the following circumstances:

  • Start BOINC and run benchmark
  • Within 5 days, restart BOINC without changing version or configuration (no benchmark runs)
  • Allow to run until 5 days after the initial benchmark.

Solution: When deciding not to run benchmarks at the intermediate restart (not needed: too recent), set did_benchmarks true anyway (on the grounds that it's a continuation of the previous session).

Note: See TracTickets for help on using tickets.