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

Reduce ops when setting exisitng execution env #9967

Merged
merged 2 commits into from
May 16, 2024

Conversation

hubertp
Copy link
Collaborator

@hubertp hubertp commented May 16, 2024

Pull Request Description

Setting execution environment to the existing one should have no effect.
Should (positively) affect startup in #9789.

Important Notes

Cancelling jobs and triggering a fresh execute job is expensive and unnecessary, especially on startup, when the result should be the same as before.

Checklist

Please ensure that the following checklist has been satisfied before submitting the PR:

  • All code follows the
    Scala,
    Java,
    TypeScript,
    and
    Rust
    style guides. In case you are using a language not listed above, follow the Rust style guide.
  • Unit tests have been written where possible.

Setting execution environment to the existing one should have no effect.
Cancelling jobs and triggering a fresh execute job is expensive and
unnecessary, especially on startup, when the result should be the same
as before.
@hubertp hubertp added the CI: No changelog needed Do not require a changelog entry for this PR. label May 16, 2024
@hubertp hubertp added the CI: Ready to merge This PR is eligible for automatic merge label May 16, 2024
@mergify mergify bot merged commit a5ca9f9 into develop May 16, 2024
37 checks passed
@mergify mergify bot deleted the wip/hubert/9789-setenv-check branch May 16, 2024 20:59
vitvakatu pushed a commit that referenced this pull request May 17, 2024
Setting execution environment to the existing one should have no effect.
Should (positively) affect startup in #9789.

# Important Notes
Cancelling jobs and triggering a fresh execute job is expensive and unnecessary, especially on startup, when the result should be the same as before.
Comment on lines +226 to +227
"-XX:ActiveProcessorCount=2",
"-Xmx8192m"
Copy link
Member

Choose a reason for hiding this comment

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

@hubertp Just randomly browsing through recent PRs, I have noticed this change. I assume it has something to do with performance. Could you share how the performance was affected? And give us more insight on why you have chosen these two cmdline options?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI: No changelog needed Do not require a changelog entry for this PR. CI: Ready to merge This PR is eligible for automatic merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants