Opened 17 years ago

Closed 17 years ago

#382 closed Defect (invalid)

Priority Option of create_work doesnt work

Reported by: dollebolle Owned by:
Priority: Undetermined Milestone: Undetermined
Component: Undetermined Version:
Keywords: Cc:

Description

Hello,

i wants to start work with different priority. for example

1 start a job with priority 1 and a job with priority 2

the priority is saved correctly to the database. my problem is, that the clients calculate both with the "same" priority. i thought, that jobs with a higher priority (here priority 2 = higher) are calculated faster than lower priority?

what i have to do, that de priority scheduling works fine? (the feeder is startet with de flag "-priority_order_create_time". is this correct??)

the server version is 511.

is this a bug in the server code? or a configuration problem? can you help me please? thank you (sorry for my bad englisch ;-) )

Change History (2)

comment:1 Changed 17 years ago by Nicolas

Trac is to report bugs, not to ask for help. See the boinc_projects mailing list.

About your problem: the only program that actually looks at the priority is the feeder. You have to start it with -priority_order, or -priority_order_create_time. Even then, it only changes the order the feeder reads them from the database, not the order they are sent to the client. And if both get sent, the client definitely doesn't use that to calculate one before the other (I think the client doesn't even get the priority).

If you need to change the order the clients calculate it (as opposed as the order the server sends them), you may want to change the delay_bound (deadline). The client will calculate those with shorter deadlines first.

comment:2 Changed 17 years ago by Nicolas

Resolution: invalid
Status: newclosed

Marking as invalid (help request, not bug report).

Note: See TracTickets for help on using tickets.