35132 Einstein@Home 2/8/2025 4:25:49 PM Requesting new tasks for Intel GPU
35133 Einstein@Home 2/8/2025 4:25:51 PM Scheduler request completed: got 0 new tasks
35135 Einstein@Home 2/8/2025 4:25:51 PM (reached daily quota of 960 tasks)
I think you need to ask Bernd about this, SOME projects limit the total number of tasks per person per day so that other people can contribute too, while SOME other projects limit tasks so that the data isn't skewed if a pc is giving errors. It's the old thing about a Scientist making a new discovery and making the statement 'it's a once in a lifetime occurrence' and the other Scientists asking 'well what is your sample size' and the first Scientist says '2'.
Last Time I did something with daily quota limits was in 2020 at which time I believed the daily quota task limit was:
32*#CPUs + 160*#GPUs
For a while when a prominent category of task had pretty short completion times on fast GPUs there was a fairly common practice in which people increased their daily quota enough not to run out of work by falsifying the number of CPUs.
You may still find some hosts posted here which have curiously high CPU counts vs. the actual reported processor chip as relic of those practices.
After I wrote that I did a search on ncpu here at Einstein, and found this thread which documents that the limit computation was increased in 2021, so perhaps it remains at
64*#CPUs + 512*#GPUs
subject to a limit of 128 CPUs and 8 GPUS.
The falsification parameter is ncpus found in cc_config.xml
I do not think the project intention of the limit is some sort of "fair" sharing among users, but rather an attempt to limit the damage done by a rogue host gone wild into infinite demand mode.
35132 Einstein@Home 2/8/2025 4:25:49 PM Requesting new tasks for Intel GPU
35133 Einstein@Home 2/8/2025 4:25:51 PM Scheduler request completed: got 0 new tasks
35135 Einstein@Home 2/8/2025 4:25:51 PM (reached daily quota of 960 tasks)
It seems like you have a complicated case of wanting to significantly increase the GPU (only BRP4) work supply and significantly reduce the CPU work supply. From what I can see, you'll likely have to make things messy, and even then it might not work. You'll have to spoof CPU in cc_config, GPU in coproc_info, adjust settings in the BOINC manager, and projects preferences on the website. There will still be a Beta app version limitation, unless you want to go the app_info route.
The problem is that the ARC750 doing BRP4 work is like a high schooler doing elementary school work. But yet, it's the only kind of work it can do. :-D
also; ARC
)
also;
ARC A750
35132 Einstein@Home 2/8/2025 4:25:49 PM Requesting new tasks for Intel GPU
35133 Einstein@Home 2/8/2025 4:25:51 PM Scheduler request completed: got 0 new tasks
35135 Einstein@Home 2/8/2025 4:25:51 PM (reached daily quota of 960 tasks)
[AF>EDLS
)
I think you need to ask Bernd about this, SOME projects limit the total number of tasks per person per day so that other people can contribute too, while SOME other projects limit tasks so that the data isn't skewed if a pc is giving errors. It's the old thing about a Scientist making a new discovery and making the statement 'it's a once in a lifetime occurrence' and the other Scientists asking 'well what is your sample size' and the first Scientist says '2'.
Last Time I did something
)
Last Time I did something with daily quota limits was in 2020 at which time I believed the daily quota task limit was:
32*#CPUs + 160*#GPUs
For a while when a prominent category of task had pretty short completion times on fast GPUs there was a fairly common practice in which people increased their daily quota enough not to run out of work by falsifying the number of CPUs.
You may still find some hosts posted here which have curiously high CPU counts vs. the actual reported processor chip as relic of those practices.
After I wrote that I did a search on ncpu here at Einstein, and found this thread which documents that the limit computation was increased in 2021, so perhaps it remains at
64*#CPUs + 512*#GPUs
subject to a limit of 128 CPUs and 8 GPUS.
The falsification parameter is ncpus found in cc_config.xml
the old thread link I mentioned is here:
https://einsteinathome.org/content/daily-task-quota#comment-190336
I do not think the project intention of the limit is some sort of "fair" sharing among users, but rather an attempt to limit the damage done by a rogue host gone wild into infinite demand mode.
[AF>EDLS
)
It seems like you have a complicated case of wanting to significantly increase the GPU (only BRP4) work supply and significantly reduce the CPU work supply. From what I can see, you'll likely have to make things messy, and even then it might not work. You'll have to spoof CPU in cc_config, GPU in coproc_info, adjust settings in the BOINC manager, and projects preferences on the website. There will still be a Beta app version limitation, unless you want to go the app_info route.
The problem is that the ARC750 doing BRP4 work is like a high schooler doing elementary school work. But yet, it's the only kind of work it can do. :-D