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] range query performance degradation when size of DB grows #156

Closed
dsukhoroslov opened this issue Feb 28, 2018 · 1 comment
Closed

[Core] range query performance degradation when size of DB grows #156

dsukhoroslov opened this issue Feb 28, 2018 · 1 comment
Assignees
@dsukhoroslov
Milestone
release 1.2.1

Comments

@dsukhoroslov
Copy link
Owner

YCSB workload E. on 20K docs, 128 threads throughput is > 3K ops
YCSB workload E. on 200K docs, 128 threads throughput is ~500 ops.

the issue is HZ query results retrieval mechnism. looks like it can be solved with new methods added in HZ 3.9.x.
dsukhoroslov added a commit that referenced this issue Mar 1, 2018
@dsukhoroslov
fixing #156
1e14d50
dsukhoroslov added a commit that referenced this issue Mar 2, 2018
@dsukhoroslov
fixed #156
1260b1e
@dsukhoroslov dsukhoroslov self-assigned this Mar 5, 2018
@dsukhoroslov dsukhoroslov added this to the release 1.2.1 milestone Mar 5, 2018
@dsukhoroslov
Copy link
Owner Author

fixed, works very well in stress tests, but does not work in unit tests for some reason

@ghost ghost mentioned this issue Jul 20, 2019
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dsukhoroslov dsukhoroslov

Labels
None yet
Projects
None yet
Milestone
release 1.2.1
Development

No branches or pull requests
1 participant
@dsukhoroslov