Which CPU projects support threading and or have optimized app_config settings? I would like to enable my CPU to crunch the tasks that do not have GPU support, but would like to optimize them for a quick turn around by enabling threading or other optimizations via the app_config.xml file if the threading support is available.

Thanks for any help, and any examples from your own app_config file.

Below is my "generic" app_config.xml, set up for a quad core, with no GPU tasks. If you are going to run GPU tasks, you want to make sure leave enough CPU cores free (HT cores may be enough) to keep the GPU fed.

Thank you for the information. I didn't know the "llr" meant it supported threading. I'll get my config all setup now.

Only the avg_cpus is needed. The max_cpus is useless in app_config multi-threading.

Anticipating a nightmare, last night I sat down and thought I'd have a go at getting multi-threading going, after a big wait because of that nightmarish anticipation. I thought I was definitely going to have to start a forum thread and basically plead everyone to cobble together a guide for me, in the form of links to the best forum threads, complete with customised and updated notes, just for me.

But I bunged Van Z's app_config file in there, modifying the relevant entries for the SoB bit, and it's doing what I want it to. I just told it to re-read the config files, didn't even close BOINC.

So cheers Van Z. and everyone else whose posts I read quickly last night.

So why do some people use a cc_config file? Would that be for a different platform, e.g. Linix? or can a cc_config file do something which app_config doesn't?

Ah I see, cheers Michael.

I should have proof-read my post before throwing caution to the wind and pressing "OK" up there, I wrote "Linix" and forgot how to use capitals.

So why do some people use a cc_config file? Would that be for a different platform, e.g. Linix? or can a cc_config file do something which app_config doesn't?

cc_config.xml is a lot harder to configure correctly than app_config.xml. If app_config.xml does what you need, you should always use it in preference over cc_config.xml.

cc_config.xml is the "anonymous platform" mechanism, where you must supply your own apps. If you want to run a custom app, that's how you do it. But you've got to configure it correctly and make sure all the files (including the app itself) are in the correct locations.

I assume you read the prior thread "App names" (including the follow-up responses). If the app begins with "llr", e.g. "llr321", it can make use of multithreading.

The different projects scale differently. For example, llrCUL is going to scale better to more threads (assuming you have the cores available) than llrTPS (generally, larger tasks scale better in my experience).

Below is my "generic" app_config.xml, set up for a quad core, with no GPU tasks. If you are going to run GPU tasks, you want to make sure leave enough CPU cores free (HT cores may be enough) to keep the GPU fed.

You will probably want to experiment to see what works best on your hardware. On the machine this app_config.xml came from, llrMEGA doesn't scale well beyond 3 cores, but if I run 3 cores, I have one sitting idle (hence running 2 2-thread tasks concurrently). On another of my machines it scales well up to 6.

<app_config>...