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

Document to increase CPUs #178

Merged
merged 3 commits into from
Jul 30, 2024
Merged

Document to increase CPUs #178

merged 3 commits into from
Jul 30, 2024

Conversation

FaroutYLq
Copy link
Contributor

This is to fit the new situation on OSG, which forbids excessive CPU usage. Otherwise, typically error will be

Excessive CPU usage. Please verify that the code is configur
ed to use a limited number of cpus/threads, and matches request_cpus.

However, I didn't figure out how many threads do alea-run_toymc is trying to open. I just put an empirical 4 here for now. Still testing...

@FaroutYLq FaroutYLq added the documentation Improvements or additions to documentation label Jul 23, 2024
@FaroutYLq FaroutYLq requested review from dachengx and hammannr July 23, 2024 20:51
@coveralls
Copy link

coveralls commented Jul 23, 2024

Pull Request Test Coverage Report for Build 10156768279

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 92.167%

Totals Coverage Status
Change from base Build 10066523505: 0.0%
Covered Lines: 1565
Relevant Lines: 1698

💛 - Coveralls

@hammannr
Copy link
Collaborator

@FaroutYLq we can merge this as a first try. Basically this means we should test a bit with 4 and see what happens? Anything particular to look out for?

@FaroutYLq
Copy link
Contributor Author

I already tested, and 4 CPUs generally work. (On the other hand, 1 CPU doesn't work anymore! Be alarmed). It would be better if we can find where multithreading happen in alea, but it might take a while and might be overkill. (I am not sure if OSG gonna keep the CPU rule for very long, so I think it doesn't worth the efforts now). Let's blindly do this for now: )

@FaroutYLq FaroutYLq merged commit 6e6d5d0 into main Jul 30, 2024
7 checks passed
@FaroutYLq FaroutYLq deleted the cpu_readme branch July 30, 2024 05:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants