That's because you didn't set up multithreading with an app_config.xml file. The net amount of work done will be similar.OK, I am in. But one day per task ?????
16 tasks at a time on a 2700x@4.2 ghz, memory 3600 with subtimings set, my fastest single-core box, but with 8c/16t
Three hours late isn't very late in a five day race.ah! poop!
I knew I wouldn't be around near GO! time. Starting at lunch was less than successful. I was hoping on good timing so that round2 would fully count. Alas, very little luck.
I'm in, but I'm very late.
OK, what do I put in it ? Windows 10 Ryzen 2700x@4.2 And where does it go ? (directory)That's because you didn't set up multithreading with an app_config.xml file. The net amount of work done will be similar.
Three hours late isn't very late in a five day race.
<app_config>
<app_version>
<app_name>llrSR5</app_name>
<cmdline>-t 8</cmdline>
<avg_ncpus>8</avg_ncpus>
</app_version>
</app_config>That sounds about right. Remember, modern Intel processors can handle 256 floating point bits per core, while TR can only handle 128. Intel put in more hardware that's mostly useless except for prime projects. (And certain other benchmarks.)ThreadRipper is horrible at this. My Haswell 5820K using 4 threads is getting a task done in two hours, but TR with 5 threads is taking 3.5 to 4 hours. I've bumped the TR up to 8 threads, but according to Orange Kid's results, it looks like 8 threads might equal 4 threads of the Haswell.
<app_config>
<app>
<name>llrSR5</name>
<max_concurrent>2</max_concurrent>
</app>
<app_version>
<app_name>llrSR5</app_name>
<cmdline>-t 8</cmdline>
<avg_ncpus>8</avg_ncpus>
</app_version>
</app_config>Did you take these run times from your account at the PrimeGrid web site? If so, then those are wrong. The bookkeeping is totally buggy as soon as you run the PrimeGrid applications multithreaded. The PG admins say the upstream boinc code is at fault.The Ryzen run times are all over the board. The only thing that seems consistent is the CPU time. Got to wonder what is doing this, but I'm 1600 miles away, so it is what it is.
The <app></app> part is not needed. For your setup, it does no harm but also has no obvious benefit.This is my app_config.xml
Don't know if the "<app></app>" part is needed, but it works for me.
Replace each of the two "8" by "6" then.Would my app_config.xml be the same for a 6 core Ryzen with SMT? Just wondering.
But I am not aware of recent & precise tests whether or not SMT is beneficial for PrimeGrid LLR applications on Zen.
<core_client_version>7.4.23</core_client_version>
<![CDATA[
<message>
WU download error: couldn't get input files:
<file_xfer_error>
<file_name>llrSR5_299573850</file_name>
<error_code>-200 (wrong size)</error_code>
</file_xfer_error>
</message>
]]>PrimeGrid doesn't seem to know how to calculate run times correctly. If you download more than one WU at a time, the run times are added together for later WUs. If you set <avg_ncpus>1</avg_ncpus> on a lower-end processor, and set your BOINC client to only use "one core", it will probably compute correctly, while using however many cores you set in the app_config. I'm not sure how to handle it when you actually need multiple WUs at a time.The Ryzen run times are all over the board. The only thing that seems consistent is the CPU time. Got to wonder what is doing this, but I'm 1600 miles away, so it is what it is.
I did some tests on my 2700x before the race and found when I disabled SMT in the bios and set the app_config for 8 mt cores, all the task downloads failed. I tried several times but could not get a successful task download. I turned SMT back on and and then task downloads were successful. Weird.
This was the error:
Code:<core_client_version>7.4.23</core_client_version> <![CDATA[ <message> WU download error: couldn't get input files: <file_xfer_error> <file_name>llrSR5_299573850</file_name> <error_code>-200 (wrong size)</error_code> </file_xfer_error> </message> ]]>
Did you take these run times from your account at the PrimeGrid web site? If so, then those are wrong. The bookkeeping is totally buggy as soon as you run the PrimeGrid applications multithreaded...