The runtime for the last few work units has jumped up considerably. CPU time and credit haven't changed noticeably, but run time has increased from 60 thousand to 90 thousand on the same machine, (very approximate - illustrates the point though).

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

The runtime for the last few work units has jumped up considerably. CPU time and credit haven't changed noticeably, but run time has increased from 60 thousand to 90 thousand on the same machine, (very approximate - illustrates the point though).

On both my crunchers the run time was 10,800 and is still 10,800.

The runtime for the last few work units has jumped up considerably. CPU time and credit haven't changed noticeably, but run time has increased from 60 thousand to 90 thousand on the same machine, (very approximate - illustrates the point though).

Because there is something else on your system making use of the CPU.

Run time  22 hours 27 min 25 sec
CPU time  11 hours 59 min 51 sec

22.5 hrs to do 12 hrs of work shows there is something other than BOINC using a massive amount of your CPU time.
Even before that, 16 hs 15 min to do 11hrs 45min of work isn't particularly good.
That's the sort of thing i would expect to see if you're transcoding videos, or doing some sort of CPU throttling.

On my system which is the one i use daily, the difference between CPU time & Run time is generally a few minutes (if that).

---

Grant
Darwin NT

There is nothing new on the system. It is certainly true that BOINC co-exists with other programs that run 24/7, Folding@Home for example, but that has been there for years. The "Sent" time shows that all of the longer running jobs were from the same download.

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

There is nothing new on the system. It is certainly true that BOINC co-exists with other programs that run 24/7, Folding@Home for example, but that has been there for years.

That would be it then.
Use Task manager to see how many cores/threads Folding is using.
If it's only using 1, then in your account, Computing preferences, Usage limits, set "Use at most xxx% of the CPUs" to 86%. If it's using 2, then set it to 75% etc.

That way Folding & BOINC won't be trying to use the same cores/threads at the same time, and your BOINC Run times will just about match (or at least be very, very close to) the CPU time.
No more taking 23 hours to do 12 hours of work.

---

Grant
Darwin NT

As I said, Folding has been running on this machine for years, the "problem" I started the thread about is VERY recent. All the tasks from that last download have completed and returned now, they show quite a variety of run times 73K to 90k. There are also other tasks downloaded the same day, but at an earlier time, that do not show the extended run time.

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

As I said, Folding has been running on this machine for years, the "problem" I started the thread about is VERY recent. All the tasks from that last download have completed and returned now, they show quite a variety of run times 73K to 90k. There are also other tasks downloaded the same day, but at an earlier time, that do not show the extended run time.

Then look at you logs and see what else was running on your machine during the period in question.

This is not a Boinc problem, this is within your machine.

As I said, Folding has been running on this machine for years, the "problem" I started the thread about is VERY recent. All the tasks from that last download have completed and returned now, they show quite a variety of run times 73K to 90k. There are also other tasks downloaded the same day, but at an earlier time, that do not show the extended run time.

As Bryn & i have both said- the problem is with other software running on your system.
And it isn't recent as you claim it is- even your older Tasks have a large difference between the CPU time & Run time, just not as large as the more recent ones.
You could do as i suggested, and improve your BOINC performance hugely, then check to see there is anything else using your CPU heavily other than Folding & BOINC, or do nothing & just live with it.
You can complain about it as a much as you like, but it's up to you to fix the issue.


Edit-
Ah, here we go. This isn't a very recent issue, at all- you posted about it over 4 years ago, and i told you how to fix it back then.
Posted: 22 Apr 2020, 6:47:42 UTC
Obviously you've chosen not to, so i'll save my time and effort for those that are interested in fixing their problems.

---

Grant
Darwin NT