Join PrimeGrid
Returning Participants
Community
Leader Boards
Results
Other
drummers-lowrise
|
Message boards :
Sieving :
After PFGW, fpsieve windows priority problem
Author |
Message |
|
Maybe it's time to change my computer... :)
When I launch fpsieve on windows, it crunches at normal priority, whatever I have specified in the parameters (-z19, -zidle, with space, no space).
It works fine on Linux. Only the windows client.
If I launch fpsieve + prpnet, prpnet is on hold until fpsieve has finished.
Does anybody have the same problems?
Thanks
____________
Badge Score: 1*4 + 1*5 + 7*6 + 8*7 + 3*8 + 1*9 = 140 | |
|
rogueVolunteer developer
 Send message
Joined: 8 Sep 07 Posts: 1256 ID: 12001 Credit: 18,565,548 RAC: 0
 
|
Maybe it's time to change my computer... :)
When I launch fpsieve on windows, it crunches at normal priority, whatever I have specified in the parameters (-z19, -zidle, with space, no space).
It works fine on Linux. Only the windows client.
If I launch fpsieve + prpnet, prpnet is on hold until fpsieve has finished.
Does anybody have the same problems?
Thanks
PFGW runs at idle priority. Some have suggested that I modify PRPNet to use the idle= parameter in prpclient.ini to tell PFGW to run in normal priority. I might do that for the next release. | |
|
Honza Volunteer moderator Volunteer tester Project scientist Send message
Joined: 15 Aug 05 Posts: 1957 ID: 352 Credit: 6,139,771,685 RAC: 2,272,291
                                      
|
It is a known behaviour to me - FPSieve prevents any other idle priority tasks from runnig, I've reported this before.
For example you can't run BOINC GPU tasks (that runs at idle CPU) while FPSieve it running on all cores - you need to leave at least one core idle.
____________
My stats | |
|
|
PFGW runs at idle priority. Some have suggested that I modify PRPNet to use the idle= parameter in prpclient.ini to tell PFGW to run in normal priority. I might do that for the next release.
Yes, I also report the same problem for PFGW.
It seems the client is launched idle, but the threads that crunch are created with normal priority, as for PFGW.
Hope this help.
____________
Badge Score: 1*4 + 1*5 + 7*6 + 8*7 + 3*8 + 1*9 = 140 | |
|
geoff Volunteer developer Send message
Joined: 3 Aug 07 Posts: 99 ID: 10427 Credit: 343,437 RAC: 0
 
|
I have made a change to set the thread priority in Windows, but I don't really understand priority in Windows so please let me know if it works as it should. The new executable is in fpsieve-0.2.3a-bin.zip
| |
|
Honza Volunteer moderator Volunteer tester Project scientist Send message
Joined: 15 Aug 05 Posts: 1957 ID: 352 Credit: 6,139,771,685 RAC: 2,272,291
                                      
|
Just tested with fpsieve 023a and it works for me - I'm able to run other idle priority tasks like MW GPU app.
fpsieve-x86_64-windows.exe --priority=idle --blocksize=1024 --chunksize=1024 --blocks=2
Perhaps smaller blocks also helps.
I'm getting up to 29.8K p/sec (4.00x2400) - no significant performance comparing default blocksize/chucksize I think.
(have not tested on servers yet if it slows down other services - I'm running the other sieve there ATM.)
____________
My stats | |
|
|
I just tested the new version with the same range and it's work fine. fpsieve was running with other clients.
Thanks a lot for the fix.
____________
Badge Score: 1*4 + 1*5 + 7*6 + 8*7 + 3*8 + 1*9 = 140 | |
|
geoff Volunteer developer Send message
Joined: 3 Aug 07 Posts: 99 ID: 10427 Credit: 343,437 RAC: 0
 
|
Thanks for testing the priority option fix, since it seems to work I have made it version 0.2.4.
| |
|
Message boards :
Sieving :
After PFGW, fpsieve windows priority problem |