Add YugabyteDB (without results because queries on AWS EC2 c6a.4xlarge w/ 500GB gp2 run tremendously slow) #380
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.
Resolves #365
On an AWS EC2 c6a.4xlarge (500GB gp2) instance, even simple queries run tremendously slow. On a local machine (AMD Ryzen 5 5600X, 32GB RAM, 1TB NVMe drive, benchmark executed in a Docker container), queries run notably faster.
Q1:
[1306.72,1268.44,1269.34]
[329.484,328.405,327.32]
Q2:
[1788.86,2214.2,2214.08]
[335.95,320.728,294.426]
The data loading time is comparable on both machines (~78 minutes).
Log files of the benchmark run on AWS EC2 (which was manually terminated during the execution of Q3) are attached.