I would guess CPU based on this comment a week ago:GPU app?
I am working on getting a new version of our code up on the server.
This new version will allow us to fit orbits on top of the other parameters we have already been fitting.
It may make sense to restrict the number of program threads to a lot less than those 16t. On modern CPUs, even running them single-threaded looks feasible. I haven't taken the time yet to measure what a good thread count would be, for host efficiency.The MW@H tasks are highly variable. Some last 1 second, I had another take 5300 seconds (x16) as they use up to 16 threads.
Example syntax:I just realized that I have yet to extend my app_config.xml to the new application.
<app_config>
<app_version>
<app_name>milkyway_nbody</app_name>
<plan_class>mt</plan_class>
<avg_ncpus>4</avg_ncpus>
<cmdline>--nthreads 4</cmdline>
</app_version>
<app_version>
<app_name>milkyway_nbody_orbit_fitting</app_name>
<plan_class>mt</plan_class>
<avg_ncpus>4</avg_ncpus>
<cmdline>--nthreads 4</cmdline>
</app_version>
</app_config>@Skillz Is it even possible to determine which YAFU tasks yield the best PPD?
On a quick look, it seems as if switching "Max # of CPUs for this project" from "No limit" to something greater than 1 causes the server to send only multithreaded tasks to the host.Unfortunately, by default folks will now have a wild mixture of multithreaded and single-threaded tasks in their workqueues. It is an open question how to prevent the downloading of single-threaded tasks if a user prefers to run multi-threaded tasks only (apart from writing an app_info.xml).
I thought I had tried that previously and it didn't work, but I'll try it again when I'm in the mood to run MilkyWay again.Try setting "Max # of CPUsfor this project" = 1. This should give you single-threaded tasks only. (But should still give you as many tasks at once as you possibly could want. Unless you dial down "Max # of jobs for this project".)
If the "Max # of CPUsfor this project" setting at 1 does not work the way you want, add the app_config.xml from #232 and change <avg_ncpus> and <cmdline> of both appversions to 1 thread. But this really shouldn't be needed anymore.
And for completeness: As @Skillz pointed out, hosts which only have 1 active logical CPU should now receive (singlethreaded) tasks. Before the new singlethreaded appversion was added by the admin, such hosts did not receive any work at all.
________
OCD edit, the "for this project" words have been removed from the preferences page in the meantime. Or they never were there and I merely imagined them.
According to today's admin update, this should be fixed now.Unfortunately, by default folks will now have a wild mixture of multithreaded and single-threaded tasks in their workqueues.
Looks like a good change though independent of contest situations, IMO.On 28 Oct 2024 Sergei Chernykh said:WU size and credits are doubled now
First of all, thanks to everyone participating in the project!
I've noticed today that solved work units come in so fast that the server can't keep up. I had to double the size of each work unit (together with the credit for it) to reduce the load on the server.
Keep crunching! Thanks again!
They restarted the African Rainfall Project (arp1) last week. Each task has got more than ten input files, and several of them are tens of Megabytes big. The result files of arp1 (seven files per result) are even larger IIRC. This is probably just too much for Krembil's internet connection.Right now I have all sorts of problems getting units from WCG, and a bunch are stuck in downloading and have been for hours.