Hi all,

How long can the tasks with "long tasks 2.00" in the name take? They've been reasonably fast for me in the past (hours, not days), but now I have a couple that have been running for approx. 2.5 and 1+ days, and the first one says it has 5+ days left and the second one says it has 8.5 days left? BOINCTasks shows these two are running at 98% and 97.6% CPU%, so they at least haven't died.

Does it make sense that I now have tasks that would be this long? If not, should I just kill them?

Thanks.

Doug

Something might be wrong with those tasks.
Use your Process Manager and see if they actually are using CPU.

I'd kill those.

Or do what the admin says in this message:
https://www.sidock.si/sidock/forum_thread.php?id=224&postid=1787#1787

Something might be wrong with those tasks.
Use your Process Manager and see if they actually are using CPU.

I'd kill those.

Or do what the admin says in this message:
https://www.sidock.si/sidock/forum_thread.php?id=224&postid=1787#1787

They are most likely using 100% CPU.

In computing options set leave on memory off, then read config files.
Suspend the task(s) then resume
Set leave in memory back on then read config files.

That will force the task(s) to restart at the last checkpoint and all should be ok.

The circumstances that led to the unit hanging hasn't changed so I just abort them to avoid the possibility the same thing happens again to the same task.

The circumstances that led to the unit hanging hasn't changed so I just abort them to avoid the possibility the same thing happens again to the same task.

No, the circumstances that led to the unit hanging are intermittent, by going back to the last checkpoint the likelihood of it happening again is the same as the likelihood of it happening in the first place.

The circumstances that led to the unit hanging hasn't changed so I just abort them to avoid the possibility the same thing happens again to the same task.

No, the circumstances that led to the unit hanging are intermittent, by going back to the last checkpoint the likelihood of it happening again is the same as the likelihood of it happening in the first place.

In other words, the chance in intermittent. I'll rather avoid it completely and await the determination of the developer.

All of my tasks are this long; which Bryn Mawr said was the intent.

My KabyLake 14nm Laptop shows 3d 4 hours left to complete which I'm not sure it can make by Jan 21.

The electric company put 4 hours of high cost peak periods that I have to pause the machines for daily. BOINC does not support 2 pauses per day. Only through task scheduler can boinccmd be used to dual pause boinc.

The laptop is low power so I pause it for one period but the servers got a dual BOINC install and so half the SiDock long run for 10 hours in daylight and the other half for 10 hours at night.

Not sure any of those can complete by the 21st running only 10 hours a day. They are server Xeons, but 4th gen and older.

They easily completed even the longest SRBase the last month on the 10 hour/10 hour dual plan.

SRBase provided us a multithread option we can setup in a app_config.xml to assure we'd meet the deadlines.

Is multithreaded planned here?

My KabyLake 14nm Laptop shows 3d 4 hours left to complete which I'm not sure it can make by Jan 21.

4 days to deadline for this tasks are added on server side (if I rightly found this computer). :) Probably that for next bunches of tasks the deadline will be extended.

would be very kind, if you can also extend the deadline for this 2 WUs

https://www.sidock.si/sidock/workunit.php?wuid=49613180
https://www.sidock.si/sidock/workunit.php?wuid=49610715

would be very kind, if you can also extend the deadline for this 2 WUs

https://www.sidock.si/sidock/workunit.php?wuid=49613180
https://www.sidock.si/sidock/workunit.php?wuid=49610715

Added. :)

I am also seeing tasks that are estimated for 8+ days for a single thread at 100% CPU on a pretty fast machine. That's not really acceptable since I share my compute resources between a few different projects. I will suspend sidock on my systems until this is sorted out.

Is multithreaded planned here?

Multithreaded tasks would be wonderful for the long WUs. I only ever crunch one project at a time so between multithreading and keeping a smaller cache, deadline issues would quickly become a thing of the past.

thank you

I am also seeing tasks that are estimated for 8+ days for a single thread at 100% CPU on a pretty fast machine.

Looks as very rough runtime estimation from BOINC. Processing of some ligands needs more time and different parts of workunit can consume very different time.
"My current record" ~30 hours on Ryzen 3900X with SMT, but not "days".
In any case - good luck! :)

Please add 5 days to all tasks for userid=364
Most will finish before that, some on faster PCs in time, but slower PCs estimate up to 9 days run time.

Paul.

Please add 5 days to all tasks for userid=364
Most will finish before that, some on faster PCs in time, but slower PCs estimate up to 9 days run time.

Added. :)

My KabyLake 14nm Laptop shows 3d 4 hours left to complete which I'm not sure it can make by Jan 21.

4 days to deadline for this tasks are added on server side (if I rightly found this computer). :) Probably that for next bunches of tasks the deadline will be extended.

That laptop was running an Einstein Intel GU task.
It lowered the CPU effective frequencies from 2400 to 1300 (which is way more severe a drain than I realized).
Stopped all new Einstein work and all but 2 are going to make the deadline wish I'd known about the ability to ask for deadline extensions:

would be very kind, if you can also extend the deadline for this 2 WUs

https://www.sidock.si/sidock/workunit.php?wuid=49613180
https://www.sidock.si/sidock/workunit.php?wuid=49610715

Added. :)

I could use another 2 days to complete the rest of these, unaborted tasks, on the one machine. I'm user 279.
Thankyou

but slower PCs estimate up to 9 days run time.

Paul.

My one machine had 20 WU over 7days left and the time left kept advancing 5 seconds every second.

Pausing/unpausing didn't help.
I gave up on them as they appeared to be hung.

Anyway, might as well d/l fresh WU's as they will have more realistic deadlines and the credit gained form a 9 day task won't be worth it.

Running on a 5900x. Before Long/Short tasks I used to crunch a unit in maybe under 3hrs. not they are averaging 1-2days with a couple running past the deadline with 4-6day estimates. Still crunching, but i've stopped new tasks for now.

can you add 4 days to these WU please:
https://www.sidock.si/sidock/workunit.php?wuid=49641040
https://www.sidock.si/sidock/workunit.php?wuid=49643250

Hi! :)

Running on a 5900x. Before Long/Short tasks I used to crunch a unit in maybe under 3hrs. not they are averaging 1-2days with a couple running past the deadline with 4-6day estimates. Still crunching, but i've stopped new tasks for now.

can you add 4 days to these WU please:
https://www.sidock.si/sidock/workunit.php?wuid=49641040
https://www.sidock.si/sidock/workunit.php?wuid=49643250

Added. :) New tasks is really long. Most of them between 20 and 32 hours. But if you see tasks with estimation like "days" you can check it properties in BOINC Manager: "CPU time at last checkpoint" and "CPU time". If it values very differs (for 1 hour, for example) - task is hung and need a restart. (For example - stop BOINC and start it again). Also, in beginning of task it can be a rough estimation.

Good luck!