I think I know what it is. I come back to this project intermittently and this time I did so with a VM that hadn't been on it before. Of course it put me on a limited number of work units until I return some successfully. I aborted the batch 1005 unit I had and the other three are still running. I'll just have to wait until I return at least one successful unit.

CPDN models are very floating point intensive. Since a cpu core only has one set of floating point units, two threads have to compete for resource. That's why your throughput drops.

That's probably why there can be large discrepancies between Elapsed Time and CPU Time. I've seen Elapsed Time being days longer than CPU Time.

And because the boinc client suspends the task, for whatever reason.

Confirmation from the S.Korean scientists that the remaining wah2 batches will be released sometime early March.

---

---
CPDN Visiting Scientist

What can we do about systems like host 1549227?

The anonymous owner grabbed 16 tasks for their 8 core Ryzen on 19 February: 13 of them have returned just one trickle each since then. One has crashed, showing many, many quit requests from BOINC: I got the resend, which is how it came to my attention.

Use at most x% of cpu time should be removed from boinc source code.

The anonymous owner grabbed 16 tasks for their 8 core Ryzen on 19 February: 13 of them have returned just one trickle each since then. One has crashed, showing many, many quit requests from BOINC: I got the resend, which is how it came to my attention.

Either the tasks will crash, (eventually) complete, or timeout and be reassigned. The timeout is only 3 months now on the tasks, so they won't sit churning for a year like they used to. I'm certain there are plenty of Windows machine owners who've forgotten they have BONIC requesting CPDN tasks, it's been so long since there's been a solid supply of them (the past few, if I recall, were grabbed within a day or two - not that this set lasted too much longer).

Some of my machines compute a lot faster than others, though I try very hard to make sure they're making steady progress (they S3 suspend at night because I'm doing the work from an off-grid solar install - though my new battery pack is letting me run some of them through the night).

Use at most x% of cpu time should be removed from boinc source code.

I believe the core BOINC software forums would be a good place to discuss that. Does it interact particularly badly with CDPN tasks or something? I've never actually used it.

I believe the core BOINC software forums would be a good place to discuss that. Does it interact particularly badly with CDPN tasks or something? I've never actually used it.

I have only used it to test what happens but have never had a problem with it. As well as the BOINC fora, I would suggest the git-hub noticeboards would be the place to discuss the merits of removing it from the code. The developers don't hang out on the BOINC fora much with the exception of Charlie Fenton who has been very helpful with sorting out Mac issues.

What can we do about systems like host 1549227?

We used to have a system for reporting machines that crash absolutely everything. (The main reason for this was the machines missing 32bit libraries in Linux. That system seems to have gone by the board, probably because of lack of time from Andy to administer it. Which reminds me, the VM I have just set up of Ubuntu24.04 doesn't have them yet! You could drop an email to Andy Richard.

News from CPDN.

New batches are being prepared for the East Asia 25km configuration. They will all use the Windows-only wah2-ri v8.29 app. Assuming tests go ok they should be out in the next week or two. There is also some more New Zealand 25km work planned but that's not ready for immediate release.

There is some linux work on the near horizon for the HadAM4 app. Just checking recent tests are ok before those go out.

---

---
CPDN Visiting Scientist

Thanks Glen. I am down to one second attempt that came in this morning.

sigh

WCG's feeder is down, Rosetta's out of tasks again, and my compute rigs are all...



There's a lot of silicon impatiently waiting for things to chew on! Windows, Linux, MacOS 32-bit Intel, whatever!

And it's sunny enough, with the new battery bank, to be able to mostly crunch 24/7 this year!

Maybe https://www.sidock.si/ ?
You can even recompile cruncher from source with -march=native if you want..

And it's sunny enough, with the new battery bank, to be able to mostly crunch 24/7 this year!

About to build my new home, off grid, 4.92kW panels (12 x 410W), 48V 280Ah batteries (4 x 12V 280AH LiFePO4) to start with. So Boinc running a little, apart from winter, winter is just enough for lights, computer games, TV, fridge, freezer, probably. UK rule of thumb for this system is 205W 24/7 in winter, 1.025kW 24/7 in summer. Got a damn good deal on the batteries and the panels, trade prices!

Next Weather@Home batches going out today. Same region, EAS25, as previous 1006 & 1007, so expect the same runtimes etc.

Should be 3 new batches released.

If there are any problems, please report to a new thread, not this one!

---

---
CPDN Visiting Scientist

Next Weather@Home batches going out today. Same region, EAS25, as previous 1006 & 1007, so expect the same runtimes etc.

My pipsqueak Windows 10 machine got one, Batch 1008. Predicting about 17 1/2 days, but it will probably finish in about half that time. It has about a half hour on it now. McAfee had no trouble with it.

---

It's great there's new work, but it'd be even better if it would actually let machines requesting it HAVE some.

It's great there's new work, but it'd be even better if it would actually let machines requesting it HAVE some.

At least as of right now, there's nothing meaningful in the unsent queue. The Windows machines tend to suck up the tasks in a prompt hurry.

As if on cue... There are two more batches planned for the Weather@Home EAS25 region ASAP. However, these have been put on hold temporarily while we investigate the error behaviour of the current 1008 batch.

---

---
CPDN Visiting Scientist