LHC@home

I see that one WU allocates 32 cores and then inside there is 6 processes cmsExternalGene using 1 core each.

What is the expected max number inside, as CP say seems like maybe 8?

When you look at your computers tasks on the website, are they vbox64 or vbox64_mt_mcore_cms? Ben's computer was showing one off each outstanding / in progress

If the #cores must be configured at batch creation time, then please make a decision.

Either keep only the singlecore app
or drop the singlecore app and send out a multicore with a fix #cores that is in sync with the backend.

Do not mix batches having different core settings as this would break BOINC's work fetch, runtime estimation, credit system ...

Any word on release to production yet?

Yes, I am *clearly* a trouble maker after all. Utterly incorrigible. ;)

Thanks for that, I'm looking for ward to seeing how these run in production.

So do the multicore work units actually get 4 times the work done using four cores?
I'd check myself but when I asked to join -dev I was told I wasn't required.

It needs to be clarified whether

1. a workflow batch at the backend must be configured to run on n cores before any work is sent out

2. a task on a volunteer VM can forward it's own #cores to the CMS app and CMS uses this #cores.
Like:
2-core VM -> 2-core CMS
4-core VM -> 4-core CMS


Sending out something like fix n-core CMS tasks to a VM not running n cores makes no sense.

Yes, we're working on it, but it takes time. Currently we have some two-core and some 4-core jobs in the queue. These will only run in -dev. Let us know how you get on. I'll put some single-core jobs up as well, so people not in -dev can get some work too.

Hmm, there is a little problem with that -- The workflow manager is holding that batch in acquired status while the 2- and 4-core batches run and probably won't start it running until those queues start running dry, which could take some time!

We still don't have any 1-core jobs available for CMS@Home "production". Federica is going to kill her 2-core workflow, so then hopefully the workflow-manager will notice that there aren't many jobs in the queue, and will move my workflow into the "running" state.

Yes, we're working on it, but it takes time. Currently we have some two-core and some 4-core jobs in the queue. These will only run in -dev. Let us know how you get on. I'll put some single-core jobs up as well, so people not in -dev can get some work too.

Hmm, there is a little problem with that -- The workflow manager is holding that batch in acquired status while the 2- and 4-core batches run and probably won't start it running until those queues start running dry, which could take some time!

Yes, we're working on it, but it takes time. Currently we have some two-core and some 4-core jobs in the queue. These will only run in -dev. Let us know how you get on. I'll put some single-core jobs up as well, so people not in -dev can get some work too.

I think multi-core not yet arrived. Not sure what I could see, because the Consoles do not display usefull info.
I created a dual core VM (not 4 cause other duties on that laptop), but I see only 1 cmsRun using 100% CPU and some other cpu-usage from other processes.
Total 102% CPU after 24 minutes.

new new tasks since last night :-(

sorry, should read "NO new tasks ..."

Ivan wrote on Feb. 14:

We've been having some problems lately as we prepare to allow multi-core jobs to be run in CMS@Home (you've probably noticed...). Unfortunately some of the configurations are beyond our control, and we have to request changes as we find problems and determine a potential fix for them.
We ask for your patience at this time while we work through the difficulties, and would fully understand if you chose to pause your participation in the project while we try to get on top of things.

Ivan, any progress yet ?

queue is empty :-(