Skip to content

Add YugabyteDB (without results because queries on AWS EC2 c6a.4xlarge w/ 500GB gp2 run tremendously slow) #380

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

michaelkoepf
Copy link
Contributor

@michaelkoepf michaelkoepf commented May 25, 2025

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:

    • EC2: [1306.72,1268.44,1269.34]
    • Local: [329.484,328.405,327.32]
  • Q2:

    • EC2: [1788.86,2214.2,2214.08]
    • Local: [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.

@rschu1ze rschu1ze self-assigned this May 26, 2025

—[YugabyteDB GitHub repository](https://github.com/yugabyte/yugabyte-db)

> [!WARNING]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's remove the warning and include results for EC2, even if slow. Being able to compare databases on the same hardware using the same queries/data is the whole point of ClickBench :-)

Copy link
Contributor Author

@michaelkoepf michaelkoepf Jun 5, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should i run it with or without modified OS settings (ulimits, transparent huge pages, etc.)?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If I see correctly, hugepages are on by default anyways and the other custom OS settings are hard limits on the number of files, CPU etc. which should also have reasonable defaults.

In that sense, I don't think we don't need to change OS settings.

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.

Add YugabyteDB
2 participants