Make Express and Promt memory configurable #4638
Conversation
germanfgv
left a comment
There was a problem hiding this comment.
Let's clarify the BaseMemory value. Other than that this seems fine.
|
|
||
| specArguments['Memory'] = baseMemory + perCoreMemory | ||
|
|
||
| baseMemory = 500 |
There was a problem hiding this comment.
From Dima's comment on Slack, I understand that we don't want to assign this 500MB base memory. We want to assign 2GB/core, and use additianal memory only in case of emergency.
There was a problem hiding this comment.
Or is it different for Express?
There was a problem hiding this comment.
As mentioned during the meeting we should fit CMS infrastructure requirements, that means 2GB/core for any type of job. With the previous formula Tier0 was given in some cases more than 2GB/core so I will start to test this PR with the runs from 2021 and start to validate which jobs were requiring more than 2GB/core
95379f9 to
9ad3c2a
Compare
|
Changes were tested with different replays. No issues to report only 1 paused job requesting more than 2Gb/core while testing with the run 347028. Same job reported here https://hypernews.cern.ch/HyperNews/CMS/get/tier0-Ops/2321.html |
Add an option to configure the max memory per core for Express and Promt configurable via Configfile.
9ad3c2a to
32c56be
Compare
germanfgv
left a comment
There was a problem hiding this comment.
Everything seems fine! Thanks for the changes @jhonatanamado
Add an option to configure the max memory per core for Express and Promt configurable via Configfile.