Hi all,

Must have been highlighted before but could not find the appropriate thread so here goes: I've noticed that I'm getting these Ocean models with status "Running, high priority". Given that I am a multi-project contributor, this is an issue for me as these large models crowd out any processing on the other projects. Aside from manually tinkering with suspending tasks, is there an easy solution that will allow me to put a cap on resources used by CPDN? I'm a bit ticked-off by this as, clearly, there is no advantage to CPDN with sole-project contributors so it seems to me it's sort of not so nice to other projects.

Kind rgds,
Umf

---

I am sure one of the moderators will pick this up but once the model has been running a while it drops out of high priority mode as it seems to overestimate the time to completion till it gets a way in. It is to do with the BOINC code that needs a deadline. CPDN tasks do not actually have a deadline though one is put in to keep the BOINC code happy. You are right this has been discussed in a number of threads previously but i can't remember the titles of the particular threads.
As someone who only contributes to other projects when there is a lack of work from CPDN it is not really an issue for me. One solution would be to edit your preferences and not accept work from the full ocean models and stick to ones like the regional models which are much shorter.

Dave

That CPDN does not have a deadline is well known to me. Are you saying that the high-priority status is not intentionally given by CPDN but assigned by BOINC due to the high time-to-completion and the short (albeit irrelevant) deadline?

In any case, If I can opt-out from the full models but retain the regional models through the preferences than I'd really like to know how.

Many thanks,
Umf

---

When people run (any) climate model, plus (any) short completion time projects, there's always going to be a problem if people starve the climate models of resources.

Think of it in terms of shopping.
If you only buy lots of small items, then they will each only need a small amount of table to put them on while you sort them out for putting away.
But if you also buy 1 very large item, then that will need a much larger area of table, otherwise it'll fall onto the floor.

In the case of your multiple projects, if you don't want anything running in high priority mode and hogging processor time, then you you need to give the longer climate models a larger Resource share.
This is set in the first lot of preferences on your project account page.

**************************

To only receive short climate models in the future, this is done in the third lot of preferences on your project account page.

Make sure that the only model types that are selected are the 3 regional ones - Pacific North West, European, and Southern Africa.
And also make sure that If no work for selected applications is available, accept work from other applications? is NOT selected.


**************************

I'm a bit ticked-off by this as, clearly, there is no advantage to CPDN with sole-project contributors so it seems to me it's sort of not so nice to other projects.

The research group running the long RAPIT models are on a tight schedule, mostly caused by all of the projects problems in the first half of this year.

You can read the thread from those people here, and the description of their experiment here.

---

Backups: Here

That seems hardly helpfull, sry. It's not that I do not want to run Ocean models, it's that I do not want the Ocean models to consume three of my four cores while my other two projects share the other only. I'd prefer a 1.333 core per project which would be expected given that each has a resource share of 100.

So I guess I'll just have to tinker with Suspend/Resume and give Ocean 1.000 core. Just did. But at least that one is running at a very high priority ;-)

---