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

Expose merge throttling parameter #581

Closed
wants to merge 5 commits into from

Conversation

vthacker
Copy link
Contributor

@vthacker vthacker commented Jun 19, 2023

Summary

On the recovery nodes we don't want to throttle merges. Throttling is useful when we want to balance indexing vs search performance.

However recovery nodes are not searchable while the recovery service is creating chunks. So we should be setting very high commit and refresh intervals ( which we have started doing last week ) and not throttling merges.

Another PR is tacking increasing the ram buffer size which also saw a significant improvement in overall throughput.

Requirements

@vthacker vthacker changed the title Kaldb recovery task should not block threads Expose merge throttling and set higher ram buffers Jun 19, 2023
@vthacker vthacker force-pushed the kaldb_recovery_task_should_not_block_threads branch from 5d1e25f to ae900b6 Compare June 19, 2023 22:13
@vthacker vthacker changed the title Expose merge throttling and set higher ram buffers Expose merge throttling parameter Jun 19, 2023
@vthacker vthacker force-pushed the kaldb_recovery_task_should_not_block_threads branch from ae900b6 to 034541a Compare June 19, 2023 22:33
@vthacker vthacker force-pushed the kaldb_recovery_task_should_not_block_threads branch from 140c697 to d62b1c9 Compare June 19, 2023 22:48
@vthacker vthacker marked this pull request as ready for review June 19, 2023 22:57
@bryanlb
Copy link
Contributor

bryanlb commented Jul 24, 2023

See #624

@bryanlb bryanlb closed this Dec 14, 2023
@bryanlb bryanlb deleted the kaldb_recovery_task_should_not_block_threads branch August 26, 2024 17:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants