Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tuning tpv rules for __DATA_FETCH__ tool #1846

Open
cat-bro opened this issue Mar 19, 2024 · 0 comments
Open

Tuning tpv rules for __DATA_FETCH__ tool #1846

cat-bro opened this issue Mar 19, 2024 · 0 comments

Comments

@cat-bro
Copy link
Collaborator

cat-bro commented Mar 19, 2024

(1) data fetch was initially given 3.8GB of RAM per job. More 95% of these jobs will not run out of memory with 3.8G. There is a small subset of jobs that have run out even with 8G, so this has been raised to 10G. It would be good to find the job types that consistently use >4GB (saved in job metric data) so that these jobs can be given mem: 4 and only the others have 10G - it will make it easier to schedule

(2) Give data fetch jobs a higher slurm priority than other jobs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant