| log in |
|
1)
Message boards :
Number crunching :
Long 2 are a joke
(Message 4854)
Posted 3 Jan 2019 by Tern Here is what I've wound up using on my 4790K, and it seems to work quite well - I DID have to add the "ncpus" in there so BOINC would report them as using 3 CPUs. I also note that usage never gets over about 130% (100% = 1 core) even though 3 are specified. Other apps run up to 287%. However, it works, I'm not going to mess with it. I've only included srbase12 here - obviously you can replicate this for the other 11... <app_config> <app> <name>srbase12</name> <max_concurrent>1</max_concurrent> <fraction_done_exact/> </app> <app_version> <app_name>srbase12</app_name> <cmdline>-t3</cmdline> <avg_ncpus>3</avg_ncpus> </app_version> <project_max_concurrent>1</project_max_concurrent> <report_results_immediately/> </app_config> I had to abort several "long3" wus as there was no way they were even going to START before the deadline. These deadlines seem very short for such long tasks - I am set for one days work plus one day extra, yet got like 10 long3's, each around 11 hours runtime, that were due three or four days later. Even if no other projects were running I couldn't have made it. It's possible that the overload was due to messing around with app_config, so I'm not sweating that yet. |
|
2)
Message boards :
Number crunching :
Long 2 are a joke
(Message 4850)
Posted 1 Jan 2019 by Tern You have all your app_versions as "srbase" and not "srbase2" "srbase12" etc... |