I think it is going to be a rare occurrence for different oifs batches to be out there at the same time.

I assume the rules don't allow wildcards?

Hi!
A new one turned up on the server status page: OpenIFS 43r3 Multi-core Linear grid tl159 l91
Multi-core sounds very interesting, how many cores? is it going well on testing?

Yes it works fine. As usual it's the integration into the cpdn framework which takes time.

As for cores, we'll probably start with two but the model performs well with more.

---

---
CPDN Visiting Scientist

Unless I have missed them through not paying attention they are still just in house testing. But I am looking forward to seeing them.

CPDN have just created the 'app' in boinc speak. There are no plans to use it on the main site, only testing for now. Still some boinc related issues to iron out.

Andy has sent some tasks out for testing. these are peaking at a bit over 9GB/task which is the highest I have seen yet I think.

There are some new OpenIFS BL app batches coming once code development & testing is complete (some time yet).

---

---
CPDN Visiting Scientist

There are some new OpenIFS BL app batches coming once code development & testing is complete (some time yet).

Yes, I wasn't expecting them to appear on the main site for a while in fact I am pretty certain there is time for those whose motherboards can accommodate it to upgrade their RAM in preparation and still have a fair old wait!

There are some new OpenIFS BL app batches coming once code development & testing is complete (some time yet).

Hurray! I have not gotten any work on my main (Linux) machine since last June (IIRC).

---

Andy has sent some tasks out for testing. these are peaking at a bit over 9GB/task which is the highest I have seen yet I think.

I checked with Andy about this as the configuration he's testing should only be ~3.5Gb. He said he's enabled boinc_diagnostics, which is a BOINC API set of functions for tracing various problems in the code. He's debugging the 'double free corruption' problem that we previously saw.

The production version of OpenIFS in the T159 configuration doesn't use anywhere near 9Gb.

---

---
CPDN Visiting Scientist

Thanks Glenn. That makes sense. I had wondered about why the usage was so high. Pleased to say they all finished with no issues my end.

The production version of OpenIFS in the T159 configuration doesn't use anywhere near 9Gb.

Does not bother me either way since I upped my RAM on my Linux machine to 128 GBytes late last year.
It has the 32-bit compatibility libraries on it, though they are not needed for OIFS programs.

Computer 1511241

CPU type 	GenuineIntel
Intel(R) Xeon(R) W-2245 CPU @ 3.90GHz [Family 6 Model 85 Stepping 7]
Number of processors 	16

Operating System 	Linux Red Hat Enterprise Linux
Red Hat Enterprise Linux 8.9 (Ootpa) [4.18.0-513.24.1.el8_9.x86_64|libc 2.28]
BOINC version 	7.20.2
Memory 	125.07 GB
Cache 	16896 KB

---