Just aborted 62895949 after nearly 12h CPU runtime and showing 45% progress.
WU's come in showing a runtime of 5.5h. I would like to see the expected runtime somewhat more accurate if WU's run normal.
There seems to be quite a big spread in runtimes. Other projects are more predictable.

The expected run time appears to be the average of your last ‘n’ work units rather than tailored to the individual WU and, as you say, there is a big spread in the size of then with most around 5 hours but some, as in the one you aborted, running for 24 hours. The credits given do reflect the run time so, if that worries you, you don’t loose out.

This topic is 1 year old. We now have checkpoints, and more accurate percent complete status.

Each tasks have 5 day deadline at the time of this reply, plenty of time for my slow intel atom N270 which mostly takes 1 to 3 days to complete 2 tasks.

Hello! :)

Tasks for target corona_NSP16_v1 much longer than for previous target and varies from ~5 hours up to ~20(!) hours for my Ryzen 3900X.
Each task (excluding last workunit of whole set) is a job for inspecting of reactions of 500 ligands with target protein, but if one ligand "looks" good, reaction with it is computed more times. If task have a subset of "good" ligands for current target, duration of its computation may be long and process should progress unevenly.

Hello! :)

Tasks for target corona_NSP16_v1 much longer than for previous target and varies from ~5 hours up to ~20(!) hours for my Ryzen 3900X.
Each task (excluding last workunit of whole set) is a job for inspecting of reactions of 500 ligands with target protein, but if one ligand "looks" good, reaction with it is computed more times. If task have a subset of "good" ligands for current target, duration of its computation may be long and process should progress unevenly.

Thanks for explaining the why as well as the what.

I have tasks running between 10 and 20 hours, which expect to run for 5 to 35 days more.

Not sure what to do about them really, since at this rate they will invariably time out.

I have tasks running between 10 and 20 hours, which expect to run for 5 to 35 days more.

Not sure what to do about them really, since at this rate they will invariably time out.

It was a fluke, by the way, none of those tasks took over 48 hours in the end.
May have something to do with recently updated chipset drivers.

Also, BOINC needs time to adjust its estimated completion times for better accuracy for any new project/new work units it encounters.