Join PrimeGrid
Returning Participants
Community
Leader Boards
Results
Other
drummers-lowrise
|
1)
Message boards :
Number crunching :
Better multi-threading
(Message 132544)
Posted 1363 days ago by GlenM74
Okidoki.... From reading this thread and others, I am seeing that an APP_Config file regardless of the setting in Primegrid Preferences should override and independantly control individuall LLR Apps.
So for PPS, PPSE, PPS Mega and TPS LLR's i have the following excerpt from App_Config
<app>
<app_name>llrPPS</app_name>
<max_concurrent>4</max_concurrent>
</app>
<app_version>
<app_name>llrPPS</app_name>
<plan_class>mt</plan_class>
<cmdline>-t 1</cmdline>
<avg_ncpus>1</avg_ncpus>
<max_ncpus>1</max_ncpus>
</app_version>
<app>
<app_name>llrTPS</app_name>
<max_concurrent>4</max_concurrent>
</app>
<app_version>
<app_name>llrTPS</app_name>
<plan_class>mt</plan_class>
<cmdline>-t 1</cmdline>
<avg_ncpus>1</avg_ncpus>
<max_ncpus>1</max_ncpus>
</app_version>
<app>
<app_name>llrPPSE</app_name>
<max_concurrent>4</max_concurrent>
</app>
<app_version>
<app_name>llrPPSE</app_name>
<plan_class>mt</plan_class>
<cmdline>-t 1</cmdline>
<avg_ncpus>1</avg_ncpus>
<max_ncpus>1</max_ncpus>
</app_version>
<app>
<app_name>llrMEGA</app_name>
<max_concurrent>2</max_concurrent>
</app>
<app_version>
<app_name>llrMEGA</app_name>
<plan_class>mt</plan_class>
<cmdline>-t 2</cmdline>
<avg_ncpus>2</avg_ncpus>
<max_ncpus>2</max_ncpus>
</app_version>
I would assume based on past working experience that this would allow 4 concurrent instances of llrTPS to run on an individual core each.... This has worked in the past.
Since the change All Sophie Germaine tasks and only Sophie Germaine Tasks are now running on 4 cores... (I7 3770K running 4 cores - 50% CPU Usage in settings to avoid HT.)
This does not happen when running PPSE or PPS.... 4 tasks run concurrently with one task per core.... PPSMega i have 2 tasks running with two cores per task but the TPS (SGS) is allocating 4 cores to a single task despite a virtually identical <APP></APP> reference as PPS... (Basically the same as PPS but with P removed and a T replaced in a copy / replace process)
The PPS's are all running to plan... as expected... just not the TPS?
Any thoughts.... Currrently in Prime Grid Preferences i have no limit on work units, with a maximum of 4 Threads per Task set.? I have set Boinc to use 50% of CPUS' to avoid HT on an I7-3770K
Any suggestions would be appreciated.
Cheers
Glen
|
2)
Message boards :
Problems and Help :
Boinc Task Queuing
(Message 126900)
Posted 1563 days ago by GlenM74
Thanks Crun-chi I will give it a crack
Cheers
Glen
|
3)
Message boards :
Problems and Help :
Boinc Task Queuing
(Message 126896)
Posted 1563 days ago by GlenM74
I crunch away quietly but have a question.... TDP19 is on of course and as per all advice, have reduced all settings to zero for store at least and additional store...
This was working great when sieving PPS and crunching SOB's and TR5's with new tasks appearing about 10 to 15 seconds before the job completed. Not crucial then... but since TD19 commenced... it takes just under 6 minutes to LLR Crunch a PPSE task and again alot less than average indicated for PPS MEGA etc... Now I am banking up 1 to 2 jobs when there is still an estimated 5 minutes to crunch on the first task... I dont mind at all, but with Primes on the Line... First in and all... Im seeing that the delay between receiving the job and starting is pushing many back to second complete... Again dont really care, but is this something that has changed because of TDP19 or has a BOINC update also potentially had a change somewhere in the options we cant see that has put in an additional buffer.
Cheers
G
|
|
