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

CI: enable jemalloc in release tests #46393

Merged
merged 1 commit into from
Jul 8, 2024

Conversation

hongchaodeng
Copy link
Member

Why are these changes needed?

Related issue number

Checks

  • I've signed off every commit(by using the -s flag, i.e., git commit -s) in this PR.
  • I've run scripts/format.sh to lint the changes in this PR.
  • I've included any doc changes needed for https://docs.ray.io/en/master/.
    • I've added any new APIs to the API Reference. For example, if I added a
      method in Tune, I've added it in doc/source/tune/api/ under the
      corresponding .rst file.
  • I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/
  • Testing Strategy
    • Unit tests
    • Release tests
    • This PR is not tested :(

@hongchaodeng hongchaodeng requested a review from a team as a code owner July 2, 2024 19:51
@can-anyscale
Copy link
Collaborator

i just run a release test on this PR, let see if it works

@hongchaodeng hongchaodeng force-pushed the test_enable_jemalloc branch from ae51a24 to 50159bf Compare July 2, 2024 23:58
@aslonnie aslonnie requested a review from can-anyscale July 3, 2024 00:48
Copy link
Collaborator

@aslonnie aslonnie left a comment

Choose a reason for hiding this comment

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

deferring this to @can-anyscale

@@ -24,3 +24,5 @@ EOF

COPY "$PIP_REQUIREMENTS" .
RUN "$HOME"/anaconda3/bin/pip install --no-cache-dir -r "${PIP_REQUIREMENTS}"

ENV LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libjemalloc.so:$LD_PRELOAD
Copy link
Collaborator

Choose a reason for hiding this comment

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

is this the final form?

should we just set an RAY_LD_PRELOAD, and set this env var when ray is launching gcs or raylet? rather than setting this as global env?

Copy link
Member Author

Choose a reason for hiding this comment

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

I think using LD_PRELOAD is fine given that the container is only for running ray workloads.

I'm fine either way. Defer to @can-anyscale on final decision.

Copy link
Collaborator

Choose a reason for hiding this comment

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

if we want this as a global feature for all release tests i think this is fine; this layer is specific to ray release tests

Copy link
Collaborator

Choose a reason for hiding this comment

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

Eventually we want to only set LD_PRELOAD for ray start command so that ONLY ray processes will use jemalloc. But I'm not sure how to do it here. I think this is good enough as a temporary thing given we will revert it back later and rely on other places to set LD_PRELOAD.

Copy link
Collaborator

Choose a reason for hiding this comment

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

this will enable jemalloc on all release tests but not in production?

so we will be testing something that is different from production?

@hongchaodeng hongchaodeng self-assigned this Jul 3, 2024
Copy link
Collaborator

@can-anyscale can-anyscale left a comment

Choose a reason for hiding this comment

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

feel free to move forward without my review as needed in the next few days (i'm ooo until tuesday)

@hongchaodeng hongchaodeng added the go add ONLY when ready to merge, run all tests label Jul 5, 2024
@jjyao jjyao merged commit 05067f4 into ray-project:master Jul 8, 2024
7 checks passed
@hongchaodeng hongchaodeng deleted the test_enable_jemalloc branch July 8, 2024 20:26
GeneDer added a commit to GeneDer/ray that referenced this pull request Jul 10, 2024
aslonnie pushed a commit that referenced this pull request Jul 10, 2024
Did some bisecting and found out this commit was causing Serve's performance test latency to spike. Reverting 05067f4 to go back to previous state.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
go add ONLY when ready to merge, run all tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants