Recently I have had a number of Long running tasks that had to be aborted after running multiple days. Has anyone else seen this. So far I have seen on two Windows PC's

Thanks
Bill F

---

In October of 1969 I took an oath to support and defend the Constitution of the United States against all enemies, foreign and domestic;
There was no expiration date.

Well, I have currently 14 pretty long running tasks, which will all need 1-2 days of CPU time, but nothing that won't finish in time.

---

Did notice more tasks with long running times recently, and some estimates that were longer than I've ever seen before. I mean, always had some tasks running for over a day, and the odd one going around 2 days, but now they seem to make up more of the total and I've even seen estimates above 3 days, though I don't know long long those actually took.

What's quite unpleasant though is when you have such tasks caught in the recent mixup, you complete them but then they got canceled and can't be validated, so you end up with days and days of lost CPU time. Have 3 pages of supposed invalids like that now, most with long running times, on top of the occasional disk limit exceeded errors that comes after a long processing time instead of early on (screenshot in case they get cleared).

[/url]

What's quite unpleasant though is when you have such tasks caught in the recent mixup, you complete them but then they got canceled and can't be validated, so you end up with days and days of lost CPU time.

AFAICT they will be validated once the in progress result is returned and the validator checks them, until than they remain as "completed, can't validate".

---

I've had many 2+ days and a 7 day. A lot of my 2+ days get thrown out as an error on my part, but who can say what I did wrong.
JimPea

Your errors are the disk limit exceeded ones that have been happening for a while. Nothing wrong on your part or with your computer.

Disk limit exceeded. Didn't know I had one, but I thankee kindly for pointing me in that direction.
JimPea

The WUs have a limit, which was set too low. It *should* be fixed now, but maybe it's not as I have reported now.

---

Hi folks.
I have a quite new and very fast computer with excess RAM, Windows 11 and when using BOINC processing I am almost always also doing other things on the computer. I'm running MilkyWay@Home and some tasks are running OK, while some get very slow. Most files I'm finding experience a slowdown at some point, going from a steady processing speed to a standstill, perhaps 3 or 4 times per file. The FIX I've found is to wait until a file that was processing OK has stalled, then select it with the cursor, choose to SUSPEND it, wait about 10 seconds and then click "Resume". This fix has an almost 100% success rate to get files back processing at the highest speed they were before. Try it.

Just FYI, I am giving BOINC files a setting of using roughly 50% of CPU power, 50% of memory (which they'll never get close to using that much), and while I let Asteroids files process as fast as the computer can take them, I noticed MilkyWay files are far slower, so I select only two or three at a time for processing, even though about 7 will run at once if I let BOINC select them at will wide open. I haven't got the BPU sensitivity engaged, because my online computer activity isn't very graphic intensive, and I do a lot of reading. Because MilkyWay files are so slow, I am now running either Asteroids or MilkyWay exclusively at any one time. When I burn through my 10 or 20 MilkyWay files then I'll suspend MilkyWay and turn on Asteroids and process 100 files very quickly.

Actually I'd expect best throughput when running both projects simultaneously, in particular on CPUs with hyperthreading, simply because it's more likely, that each application will utilize different parts of each real CPU core. The Asteroids application has AVX-512 support, the Milkyway application does not, so there's a good chance they can run on the same core without blocking each other very much. But as usual, YMMV.

---

Thanks for that info, Link. I've started running 3 or 4 Asteroid files simultaneously with MilkyWay and MilkyWay continues with no speed slowdown from the Asteroid files joining in. Figures. The Milky Way accomodates asteroids and might in fact be nothing but asteroid jambalaya. It's all the same.