LHC@home

We are very happy to announce that the LHCb application is out of beta and is now in production mode on LHC@home. Thank you all for your precious contribution.

We are grateful to have you all as part of our project.

Please, refer to the LHCb application forum for any problem or feedback.

Thanks a lot
Cinzia

We are very happy to announce that the LHCb application is out of beta ...

To get a LHCb task I still need to have "Run test applications?" ticked in my preferences.

To get a LHCb task I still need to have "Run test applications?" ticked in my preferences.

No, I just got one without it.

Thanks a lot.
It's an important piece of news.
Now balancing between sub-projects will be easier because all the sub-projects have the same level.
I hope it will avoid if a sub-project fails to stay stuck with it and server will provide other sub-project jobs, without micro-managing inside our web preferences.
It would be a good thing to adapt the flow in such circumstances (failure , overload ,lack of wus).
So we have to modify our web preferences to enable a maximum of sub-projects, (if our hardware configuration has the requirement expected...).

Today I finished 2 LHCb WUs without any obvious error except that - according to this page - the job queue seems to be empty.
https://lhcathome.cern.ch/lhcathome/result.php?resultid=136800304
https://lhcathome.cern.ch/lhcathome/result.php?resultid=136817880

As I run the VMs above the official parameters (2 cores instead of 1 and 4224MB RAM) I would ask if a member of the project team could check the scientific output.

I can't answer you.
But i find intersting what you are doing.
Can you give us the maximum of the memory used parameter in the top console (alt+F3) inside the Vm for 2-core ? (Theory , CMS , LHCb)
It may be interesting for small hosts which would want to test if 2-cores are possible or not with their ram.They would have to add 50 MB to your numbers and place them in their app_config.
Normaly the maximum of the parameter is reached after the vm is filled with the end of the net - initialisation (not necessary to wait and see all the time).
Curiously ,you use a higher amount of ram in your app_config than needed.
The initial purpose of multicore wus was to allow small hosts with less ram to do more work than with single core which requires more ram.
I don't know if giving more ram speed up the job.It seems not.
But i noticed the last job theory done with 2-core i ran used 130 % of a core that is to say the second core help to finish the job.
It seems processes are shared in particular condition between cores...
----------------------------------------------------------------------------------------------------------------------------------------------------------------
Another question :
can someone explain why when we put

for LHCb :
2 048 MB ram Memory in app_config , only 2 044 580 k appears in the total memory in the console (difference: 3 420 k)

for theory :
1-core:
630 MB ram Memory in app_config , only 615 068 k appears in the total memory in the console (difference: 14 992 k)
2-core:
890 MB ram Memory in app_config , only 877 076 k appears in the total memory in the console (difference: 12 924 k)

The difference is not proportional to the ram affected and is not constant...

There is 8MB reserved for video memory, but doesn't explain the total difference.

I wrote an answer in a new thread as it would be OT here:
https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=4248&postid=30129