Dear participants, at the start of the current search, we set a deadline for "CmDock long tasks" to 14 days. But the average time required to process a task is 40 hours. Also, we see many of uncompleted tasks which prevent completion of the set to which they belong, "produced" by the computers that get tasks and do not get in touch again. Due to these reasons, we plan:
1. To perform a gradual reduction of the deadline;
2. To implement a simple mechanism which finds computers that are lost in computing space (those who did not send requests to the server in the last m days), and mark their tasks as lost. For example, m may be 10, 8, 6 or 5.

This should not interfere with computers actually participating in the calculations, but can greatly enhance the logistics of results.

Not sure if you are aware it appears that "short tasks" are not being "sent out" even though there is short tasks ready to send. Have had no issues receiving the long tasks. As I write there are 1634 short tasks ready to send

Hello! "Short tasks" for computers with ARM CPU only. But for single-board computers like Raspberry Pi they are also long.

Thanks for information, that makes sense

Hello! "Short tasks" for computers with ARM CPU only. But for single-board computers like Raspberry Pi they are also long.

And the long ones are even longer for those!

I am currently crunching on a Long Wu sind alsmost 17 days, and it will need 3 more days. But in my account it already timed out and got assigned to a new machine. Should I abort it?
https://www.sidock.si/sidock/result.php?resultid=79849315

Best regards
Felix

Hello! "Short tasks" for computers with ARM CPU only. But for single-board computers like Raspberry Pi they are also long.

And the long ones are even longer for those!

I am currently crunching on a Long Wu sind alsmost 17 days, and it will need 3 more days. But in my account it already timed out and got assigned to a new machine. Should I abort it?
https://www.sidock.si/sidock/result.php?resultid=79849315

Best regards
Felix

Felix

I would let it run you may still get some credit

Bill F

... I am currently crunching on a Long Wu sind alsmost 17 days, and it will need 3 more days. But in my account it already timed out and got assigned to a new machine. Should I abort it?
https://www.sidock.si/sidock/result.php?resultid=79849315 ...

Consider to switch this computer to "CurieMarie Dock short tasks" only which was made for ARM SBC especially.

Good point, somehow i missed this one.
Thanks
Felix

Ah so that's why my ratio of compute for SiDock has been diverting compute from WCG.
It used to be perhaps 33% going to Sidock, now maybe 45%, all points being equal.

Is the time we see in BOINC for Deadline in UTC time or our local time? Is there any reason to keep running the task if it is past deadline?

Hello! BOINC client displays the deadline in your local time, as the computer it is running on. A task which misses the deadline still can be useful (and earn BOINC credit) for several days.