<cmdline>-t 4</cmdline>
<avg_ncpus>4</avg_ncpus>
<max_ncpus>4</max_ncpus>
In the lines above, specifically what does the "t 4" mean???
EDIT: Got the magic answer. :-)
<cmdline>-t 4</cmdline>
<avg_ncpus>4</avg_ncpus>
<max_ncpus>4</max_ncpus>
In the lines above, specifically what does the "t 4" mean???
EDIT: Got the magic answer. :-)
Last edited by Brucifer; 11-11-2017 at 06:19 PM.
4 threads I think.
yup, that's what Mike@primegrid said. :-)
I thought it was a "tpyo", but now it makes sense.
Terrific feedback, chaps.
Thank you for bringing this back to our forum for us.
. . . . . ___
. . . . . . .\___/\______
. . . . . . .\__AMD___\
\__
---------------------------------------------
Mike also said that the "<max_ncpus>4</max_ncpus>" line does not apply to the app_config.xml file and can be deleted. At some point in time someone popped it into their app_config.xml file and a large number of folks copied it. I can't remember at this moment the name of the other configuration that it is used in if not using the app_config file to set up for multi-threading. I'm currently running 4 threads on SR5 tasks taking 63 minutes per task. On the mega tasks, I run 2 threads and do one roughly every 29 minutes, which seems to be the best for the mega tasks. Why multi-threading? To try and get the task back to the server as fast as you can so that if it turns out to be prime you will hopefully beat your wingman.
<app_config>
<app>
<name>llrSR5</name>
<fraction_done_exact/>
</app>
<app_version>
<app_name>llrSR5</app_name>
<cmdline>-t 4</cmdline>
<avg_ncpus>4</avg_ncpus>
</app_version>
</app_config>
That is the contents of the app_config.xml file I'm using for crunching the SR5 tasks.
Last edited by Brucifer; 11-16-2017 at 04:49 PM.
hmmm, weird, lost the formatting when saved to the forum.
yup, sure did