On 2 of my slower computers, the computing time to complete a workunit is about 5-7 days, and on both of them, few work units failed with status "Timed out - no response" when they were nearly finished.

This is such a waste of time, which could be used for other projects, and that is why this app will not be used on my computers anymore until this problem is resolved.

There are other projects which could either calculate the remaining time precisely, and such long work unit will not be started on them, or allow going over the deadline. Rakearch project and this particular app fail in both.

On 2 of my slower computers, the computing time to complete a workunit is about 5-7 days, and on both of them, few work units failed with status "Timed out - no response" when they were nearly finished.

This is such a waste of time, which could be used for other projects, and that is why this app will not be used on my computers anymore until this problem is resolved.

There are other projects which could either calculate the remaining time precisely, and such long work unit will not be started on them, or allow going over the deadline. Rakearch project and this particular app fail in both.

Wu with such long calculation times need a longer cut-off date.

... few work units failed with status "Timed out - no response" when they were nearly finished. ...

If you mean a workunit (result) status on project web-pages - dont' worry, simply compute it to the end. Duplicate task added to the end of tasks queue and will be sent to other computer after tasks which placed in queue before it. In reality of this bunch of tasks - after several weeks. When your task has been completed, duplicated task will be dropped from queue.

And for new tasks deadline was extended to 10 days.

Thx

After one week of waiting, when the remaining time was for a couple of days stalled on 1 day, one of my weak computers would finish one wu in 16 days.
The estimated time for this work unit is completely out of reality.

And to be honest I would consider splitting this work in smaller chunks because on 1 core Zen 4 it also takes long 54 hours to complete and there is still the issue with wrong calculation of estimated time so it could look like it is stalled for some users.

I can confirm one workunit number 95792139 is Completed and validated with runtime of 1,305,936.29 second = 15.115 days.

It's very limited bunch of tasks - 23664 workunits only. More than 3800 already completed.

Program
Spectra of Latin squares 3.03

File name
wu_e1074_n12_ls_t_spectrum_loop_all_exps_sq6091_val13514
Status
Executing
Received
6/5/2025 1:03:30 PM
Reporting for
6/15/2025 1:03:32 PM
Estimated computation size
500,000 GFLOPs
Processor time
1:58:52 PM
CPU time since checkpoint
1:58:52 PM
Elapsed time
2:01:45 PM
Estimated time remaining
3:51:18 AM
Progress
91.785%
Virtual memory size
73.98 MB
Task size
80.64 MB
Map
slots/20
Process ID
3088
Progress rate
6,480% per hour
Executable
rake_lsspectra_wrapper_windows_intelx86_64.exe

anyone else having this problem
keeps dropping back to 92% and that has happened multiple times
aborting 10 pieces after 13 hours is a waste
continue or take a loss

Unfortunately I broke everything down
because of 92% to 93 and back to 92 and that followed for 2 hours
too much for little
greetings