Greetings!

Where does BOINC / sidock get the initial value for initial time remaining??
Today, 20 Nov 2022, I get WU with an initial value of 16 minutes, 36 seconds.
As it executes past 17 minutes, the time to complete advances to 5 hours, 18 minutes and is advancing.

One disadvantage is that BOINC grabbed a lot of sidock WU with the short estimated times when it obtained WU from sidock.
Now, other projects are not getting a chance.

Is this a bug?
Should I rerun benchmarks?

Thanks in advance!!

Jay

Hello!
I think that is caused by imbalance in the estimation of the task completion time. We fixed it and watching.

Hello!
I think that is caused by imbalance in the estimation of the task completion time. We fixed it and watching.

An oddity for you, I had a job running quite happily, then I rebooted the machine (Linux Mint 20.3, Boinc 7.20.2) and the figures jumped to 9.25 hours elapsed and 102 days remaining.

Over the next 1.5 hours this changed to 10.75 hours elapsed and 2 days 7 hours remaining :-


Application
CurieMarieDock on BOINC + zipped input, checkpoints and progress bar 2.01
Name
corona_TMPRSS2_v1_sample_01502800_r2_s-25
State
Running
Received
Mon 21 Nov 2022 01:02:59 GMT
Report deadline
Fri 25 Nov 2022 23:09:29 GMT
Estimated computation size
100,000 GFLOPs
CPU time
10:44:46
CPU time since checkpoint
00:00:19
Elapsed time
10:54:24
Estimated time remaining
2d 02:58:38
Fraction done
17.625%
Virtual memory size
211.46 MB
Working set size
120.39 MB
Directory
slots/5
Process ID
2382
Progress rate
9.720% per hour
Executable
cmdock-boinc-zcp_wrapper_2.1_x86_64-pc-linux-gnu


I have not seen this behaviour before, could it be related?