Message boards : CMS Application : Why CMS task downloads don't behave like Theory or Atlas tasks do?
Message board moderation

To post messages, you must log in.

AuthorMessage
Harri Liljeroos
Avatar

Send message
Joined: 28 Sep 04
Posts: 442
Credit: 23,611,162
RAC: 14,337
Message 42912 - Posted: 26 Jun 2020, 9:19:27 UTC

Because the LHC servers take a break on Saturday, I enabled CMS tasks for my main host which is normally doing just Theory and Atlas tasks. My preferences are set to 'No limit' for tasks to download, Theory and Atlas both get only maximum 8 tasks at the same time but CMS went and downloaded 184 tasks (estimated runtime about 2400 hours). The cache is set to 0.4+0,1 days. I probably don't have a problem getting them all done before deadline but this seems still excessive amount of tasks to get at one go.

Why there is such a difference how these sub-projects download tasks?
ID: 42912 · Report as offensive     Reply Quote
maeax

Send message
Joined: 2 May 07
Posts: 963
Credit: 34,055,150
RAC: 9,069
Message 42913 - Posted: 26 Jun 2020, 10:21:43 UTC - in response to Message 42912.  

CMS show 611 tasks per day are possible for your host in Computer-prefs.
Maybe, the scheduler have no limit for downloading (app_config for example).
ID: 42913 · Report as offensive     Reply Quote
Harri Liljeroos
Avatar

Send message
Joined: 28 Sep 04
Posts: 442
Credit: 23,611,162
RAC: 14,337
Message 42914 - Posted: 26 Jun 2020, 10:25:54 UTC - in response to Message 42913.  

That could be it. My opinion is that such a difference between sub-projects shouldn't be used. The configurations on server side ought to be similar.
ID: 42914 · Report as offensive     Reply Quote

Message boards : CMS Application : Why CMS task downloads don't behave like Theory or Atlas tasks do?


©2020 CERN