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.

Sign up for GitHub

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

Jump to bottom

[Core] A way to disable RAY_task_events_report_interval_ms for particular actor. #42076

Closed
jjyao opened this issue Dec 21, 2023 · 6 comments · Fixed by #42431
Closed

[Core] A way to disable RAY_task_events_report_interval_ms for particular actor. #42076

jjyao opened this issue Dec 21, 2023 · 6 comments · Fixed by #42431
Assignees
@rickyyx
Labels
core Issues that should be addressed in Ray Core enhancement Request for new feature and/or capability P0 Issue that must be fixed in short order performance ray 2.10 release-blocker P0 Issue that blocks the release stability

Comments

@jjyao
Copy link
Contributor

jjyao commented Dec 21, 2023

Description

For Serve, we want to disable RAY_task_events_report_interval_ms for proxy and replica actors since they introduce lots of traffic to GCS and those traffic cost money in the multi-AZ setup.

Use case

No response
@jjyao jjyao added enhancement Request for new feature and/or capability triage Needs triage (eg: priority, bug/not-bug, and owning component) core Issues that should be addressed in Ray Core labels Dec 21, 2023
@jjyao
Copy link
Contributor Author

jjyao commented Dec 21, 2023

cc @rickyyx @rkooo567 @edoakes

@rkooo567
Copy link
Contributor

let's fix this in 2.10?

@rkooo567
Copy link
Contributor

maybe we can have optional field to disable task metric collection?

@rickyyx
Copy link
Contributor

rickyyx commented Dec 22, 2023

Does it work with runtime env on the actor?

@jjyao
Copy link
Contributor Author

jjyao commented Dec 22, 2023

Yea, that'll probably just work.

@rickyyx rickyyx mentioned this issue Dec 28, 2023
Closed
@jjyao jjyao added P1.5 Issues that will be fixed in a couple releases. It will be bumped once all P1s are cleared ray 2.10 P1 Issue that should be fixed within a few weeks and removed triage Needs triage (eg: priority, bug/not-bug, and owning component) P1.5 Issues that will be fixed in a couple releases. It will be bumped once all P1s are cleared labels Jan 8, 2024
@rickyyx rickyyx self-assigned this Jan 12, 2024
@jjyao jjyao added P0 Issue that must be fixed in short order and removed P1 Issue that should be fixed within a few weeks labels Jan 12, 2024
@rickyyx rickyyx mentioned this issue Jan 16, 2024
Merged
8 tasks
@jjyao jjyao added the release-blocker P0 Issue that blocks the release label Feb 21, 2024
@khluu
Copy link
Contributor

khluu commented Feb 29, 2024

ETA fixed by Feb28/29 https://anyscaleteam.slack.com/archives/C01DVKB5SHE/p1709166053311979?thread_ts=1709165365.785589&cid=C01DVKB5SHE

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rickyyx rickyyx

Labels
core Issues that should be addressed in Ray Core enhancement Request for new feature and/or capability P0 Issue that must be fixed in short order performance ray 2.10 release-blocker P0 Issue that blocks the release stability
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[core][enable_task_events] Options to disable task tracing on task/actor rickyyx/ray
5 participants
@jjyao @rickyyx @rkooo567 @khluu @anyscalesam