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

Making shard throughput configurable #5183

Merged
merged 1 commit into from
Jul 2, 2024
Merged

Making shard throughput configurable #5183

merged 1 commit into from
Jul 2, 2024

Conversation

fulmicoton
Copy link
Contributor

No description provided.

@fulmicoton fulmicoton force-pushed the change-shard-limit branch 2 times, most recently from 804f7b2 to 21f0ffc Compare July 1, 2024 05:32
@fulmicoton fulmicoton changed the title Changing shard throughput limit to 20mb Making shard throughput configurable Jul 1, 2024
@fulmicoton fulmicoton force-pushed the change-shard-limit branch from 21f0ffc to 29a9672 Compare July 1, 2024 05:45
@fulmicoton fulmicoton requested a review from trinity-1686a July 1, 2024 05:56
@github-actions GitHub Actions
Copy link

github-actions bot commented Jul 1, 2024

On SSD:

Average search latency is 0.996x that of the reference (lower is better).
Ref run id: 2374, ref commit: f4e5710
Link

On GCS:

Average search latency is 1.2x that of the reference (lower is better).
Ref run id: 2375, ref commit: f4e5710
Link

@fulmicoton fulmicoton merged commit be20923 into main Jul 2, 2024
5 checks passed
@fulmicoton fulmicoton deleted the change-shard-limit branch July 2, 2024 07:32
fulmicoton added a commit that referenced this pull request Jul 5, 2024
@fulmicoton
Making shard throughput configurable (#5183)
bec4aaa
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@trinity-1686a trinity-1686a trinity-1686a approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@fulmicoton @trinity-1686a