Please fix your schedules for tasks being sent out. These extremely short turnaround times are unmanageable for probably the majority of users attached to the project. This is a waste of computing resources, yours and our upload/download Internet bandwidth.

Please explain what is the reason you need them back so soon?

Ridiculous! 20 minutes deadline on recently sent out tasks.
Example:
Task 171645641

Sent	20 Nov 2025, 19:56:18 UTC
Report deadline	20 Nov 2025, 20:16:18 UTC

---

I brought it up before with a 2 hour deadline

https://rake.boincfast.ru/rakesearch/forum_thread.php?id=359#1961

mmonnin wrote:

I brought it up before with a 2 hour deadline

https://rake.boincfast.ru/rakesearch/forum_thread.php?id=359#1961

Indeed you did. But it appears it went in one ear and out through the nose with out even touching the brain of the project admin.

These tasks were very short - about 1..2 minutes for an "average" computer. And they were successfully computed.

These tasks were very short - about 1..2 minutes for an "average" computer. And they were successfully computed.

Even if they very short running tasks the deadline/turn around time should be more reasonable.

As others have said previously At least a one day minimum.

---

Small computational complexity reduces lost of really performed computations to values tending to zero. The computer either received task, immediately computed it and return it, or simply did not start computations.
"Full push, no risk". Max Verstappen. :)

Otherwise, there will always be 1% of tasks that have not started and processing of tasks bunch will last not hours but days.

hoar, short deadline tasks are a waste of time, Running these tasks interrupt other work losing more time than it takes to actually run them. These are 100% a F'ing waste of time. No task should have a deadline of less than 2-3 days no matter the run time. Repeatedly setting stupid deadlines shows you have no concern for the people that support your project and that you're just a greedy admin to no respect for your volunteers or the admins of other projects that you just interrupted.

Hello!
If computer is involved in more than one project, BOINC client balances the time consumed by each project based on the configured priority. If any project reached the quota, BOINC Manager simply does not request tasks for it. And when one of task is paused due to start of another task, it is not interrupted but is frozen in memory and restarts later without of CPU time loss. Unless, of course, default value for setting "Leave non-GPU tasks in memory while suspended" has been changed.
I am cruncher also, not only project admin. :)

---