Opened 14 years ago

Closed 14 years ago

#1034 closed Defect (fixed)

--max_granted_credit not respected by fallback credit calculation mechanism

Reported by: dhardy Owned by:
Priority: Undetermined Milestone: Undetermined
Component: Undetermined Version: 6.10.58
Keywords: Cc:

Description (last modified by Nicolas)

We (malariacontrol.net) recently had a problem where PFC was too high for some hosts (or in some cases still is). This has resulted in credits being calculated using an alternate mechanism:

        if (pfc > wu.rsc_fpops_bound) {
            log_messages.printf(MSG_NORMAL,
                "[credit] PFC too high: %f\n", pfc*COBBLESTONE_SCALE
            );
            pfc = wu_estimated_pfc(wu, app);
        }

Unfortunately in our case this wasn't always correct. The attached patch at least allows the --max_granted_credit mechanism to still limit the credit granted.

Attachments (1)

sched_credit.patch (1.2 KB) - added by dhardy 14 years ago.
patch against boinc/sched/credit.cpp

Download all attachments as: .zip

Change History (3)

Changed 14 years ago by dhardy

Attachment: sched_credit.patch added

patch against boinc/sched/credit.cpp

comment:1 Changed 14 years ago by Nicolas

Description: modified (diff)

comment:2 Changed 14 years ago by davea

Resolution: fixed
Status: newclosed

(In [22793]) - client, acct manager protocol:

allow <no_cpu>, <no_cuda> and <no_ati> bools within <account> in reply message. They suppress work fetch for that resource type from that project.

  • scheduler:

check max_granted_credit after wu.rsc_fpops_bound, so that max_granted_credit will be enforced even if wu.rsc_fpops_bound is absurdly high Fixes #1034. From Diggory Hardy.

Note: See TracTickets for help on using tickets.