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

Only read process tree once per job_dispatch report #9322

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

JHolba
Copy link
Contributor

@JHolba JHolba commented Nov 22, 2024

Related to #9212

Approach
Only call process.children(recursive=True) once per report.

  • PR title captures the intent of the changes, and is fitting for release notes.
  • Added appropriate release note label
  • Commit history is consistent and clean, in line with the contribution guidelines.
  • Make sure unit tests pass locally after every commit (git rebase -i main --exec 'pytest tests/ert/unit_tests -n logical -m "not integration_test"')

When applicable

  • When there are user facing changes: Updated documentation
  • New behavior or changes to existing untested code: Ensured that unit tests are added (See Ground Rules).
  • Large PR: Prepare changes in small commits for more convenient review
  • Bug fix: Add regression test for the bug
  • Bug fix: Create Backport PR to latest release

@JHolba JHolba self-assigned this Nov 22, 2024
@JHolba JHolba added the release-notes:improvement Automatically categorise as improvement in release notes label Nov 22, 2024
@JHolba JHolba changed the title Only get process tree once per report Only read process tree once per job_dispatch report Nov 22, 2024
with (
contextlib.suppress(NoSuchProcess, AccessDenied, ZombieProcess),
child.oneshot(),
):
memory_rss += child.memory_info().rss
cpu_seconds += child.cpu_times().user
return (memory_rss, cpu_seconds, oom_score)
return (memory_rss, cpu_seconds, oom_score, pids)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this pids tested somewhere?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-notes:improvement Automatically categorise as improvement in release notes
Projects
Status: Ready for Review
Development

Successfully merging this pull request may close these issues.

2 participants