-
Notifications
You must be signed in to change notification settings - Fork 727
Decrease YDB CPU consumption in docker and some tests #27759 #28405
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
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -116,7 +116,7 @@ actor_system_config: | |||||
| name: "IC" | ||||||
| time_per_mailbox_micro_secs: 100 | ||||||
| scheduler: | ||||||
| resolution: 256 | ||||||
| resolution: 1024 | ||||||
|
||||||
| resolution: 1024 | |
| resolution: 256 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The healthcheck interval change from 1s to 60s significantly reduces overhead but increases the time to detect container failures from 1 second to 60 seconds. Consider if this detection latency is acceptable for your deployment scenarios, or use an intermediate value (e.g., 10-30s) to balance CPU usage with failure detection speed.