Join PrimeGrid
Returning Participants
Community
Leader Boards
Results
Other
drummers-lowrise
|
1)
Message boards :
Project Staging Area :
primegrid sr2sieve 1.11 above normal priority?
(Message 11185)
Posted 5457 days ago by Brickhead
I have 24 cores running PPS Sieve atm, and all are my own (including the DC), so nothing business critical. Just checked, and runtime priority change is disallowed in Windows 2003-64 (DC or member) and XP-64 (member). I'll continue to let any raised-priority WUs finish whenever I don't need that particular machine's services.
Oh, and it's no news that Lennart will chew through his part and then some, I expect Intel to build a separate manufacturing plant just for him :D
|
2)
Message boards :
Project Staging Area :
primegrid sr2sieve 1.11 above normal priority?
(Message 11180)
Posted 5457 days ago by Brickhead
Today, I found 12 of them.
I solve this issue by editing pps_sr2sieve_?????_cmd and changing wrong parameter (if not yet started) or simply by lowering priority in taskmanager (if started)...so no killing.
Brickhead - if you kill a result, wouldn't it be resent again (to me, lennart or whoever).
Anyway, it's time consuming to monitor and baby-sit all machines...
Changing priority on those processes is not something I'm allowed to do as a mere domain admin (I've tried). How did you do that?
I am aware that any of us might get the same WU again (if it hasn't reached one of its limits), and I'd prefer to just leave those WUs alone and hope they'll finish soon. But when, for example, a domain controller takes forever to respond to authentication requests, that's not an option.
|
3)
Message boards :
Project Staging Area :
primegrid sr2sieve 1.11 above normal priority?
(Message 11173)
Posted 5457 days ago by Brickhead
Confirmed, I killed 7 of the above-normal priority processes today (and some a few days ago).
EDIT: Any chance of having the remaining resource-hogs sought out and killed before they are sent (or re-sent)?
|
4)
Message boards :
Proth Prime Search :
PPS Sieve
(Message 11102)
Posted 5461 days ago by Brickhead
Priority seems ok now, consistent with the separate thread about the issue.
A couple of typical WU times on an OC'ed Xeon X3360 (similar to C2 Q9550):
Outcome | Client | CPU time | granted credit
Success | Done | 7705.86 (2h 8' 25.86") | 220.00
Success | Done | 5397.31 (1h 29' 57.31") | 0.00
1.11 takes roughly 30% less time than 1.05 :)
(I'm slightly puzzled about the zero credit though)
|
5)
Message boards :
Proth Prime Search :
PPS Sieve
(Message 11091)
Posted 5462 days ago by Brickhead
Sorry to be the bearer of bad news, but we do have priority issues again.
primegrid_sr2sieve_1.11_windows_x86_64.exe; Above Normal priority :(
EDIT: This is not consistent though, some instances run correctly at Low priority.
|
|
