Java driver benchmarks #11
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thank you for the contribution! @avelanarius you're the most familiar with java driver, could you review when you get a moment? |
Bouncheck
force-pushed
the
java-driver-benchmarks
branch
from
bbd4b06 to
ad0ee0f
Compare
|
I've modified 3.x-async version according to reviews and updated PR message. |
Bouncheck
force-pushed
the
java-driver-benchmarks
branch
from
ad0ee0f to
9aed68a
Compare
Bouncheck
force-pushed
the
java-driver-benchmarks
branch
from
9aed68a to
fc1ed24
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds 3 separate java-driver benchmarks.
Java-driver-3.x and java-driver-4.x benchmarks were inspired by gocql and cpp implementations.
They use multiple threads with blocking
executecalls. The intent was to make them similar enough to other implementations thus more comparable with them.Java-driver-3.x-async runs
config.concurrencymany Futures that will chain with itselves using callbacks until allconfig.tasksrequest will be sent. Tasks are split evenly except for last <division remainder> tasks which are additionally assigned to single future.Fixes #8.