For those interested in how their systems work with a high memory demand, there are a bit over a thousand task going on CPDN now. The cruncher needs to opt in to running these and they require 26GB of RAM to run. The most recent clients will not attempt to run them unless that amount of RAM is free.

That's 26GB of RAM per Task?

---

Grant
Darwin NT.

Yes, per task!!!!!!!!!

Went to the site for a looksee, that huge RAM requirement isn't all-
LINUX only.
4 cores per Task.
4.5GB for a checkpoint file!
Looks like it's a 22MB result file?
4-6 days runtime.

So your disk & Internet connection are going to get a bit of a workout as well.

---

Grant
Darwin NT.

Linux only. Though some are running the tasks using VB or WSL/
90x400MB uploads means on my bored band there will be quite a delay between the task finishing and reporting once all the uploads have gone through.

4-6 days runtime.

I have one just over 12 hours in and it is running a tad over 28%/day. That one is in VB. Once the other tasks finish on the host machine, I am hopeful tasks there will finish in just under 3 days.

One other thing I should have mentioned, no one will get any of these tasks unless they opt in under project settings on the website. Glenn did look at what percentage of machines are capable of running these tasks but I can't remember what he found without looking for the post.

Server status shows they as all gone.

I haven't seen them use 25GB yet, usually somewhere in the teens of GB. It does vary a lot. Each BOINCTask interval update it can vary a couple GB up and down so the memory transfer systems are getting a workout too. I don't recall any kind of BOINC app vary so much in memory usage across the run time. 7950x 1d3hr clock time, 3d5 CPU time 18% completed.

Server status shows they as all gone.

Not akll gone but paused while Glenn discusses with the project whether to reduce file upload size.

I don't recall any kind of BOINC app vary so much in memory usage across the run time.

The single core OIFS tasks did this as well, with memory useage varying between about 1GB and 8 GB. It means that is was possible to run more at once than in theory was possible so long as they didn't peak at the same time. These tasks use code from ECMWF that originally ran on super computers so compared with that the peak memory requirements are very low! These ones are at a higher resolution than previous batches which is why they produce such massive amounts of data and require so much memory.

New batch of these has gone out. 2,000 tasks. About 15% less total output but it still produces data a lot faster than my bored band connection can send it back to Oxford. There will be in the region of 39 uploads of 600-700MB each. Another consideration if you are short on disk space should Oxford's interweb go down and the uploads back up.

Hopefully, most machines with enough RAM to run these will also have the disk space!