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.

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

Split database test into separate read and write tests #10

Open
ottok opened this issue Oct 23, 2019 · 0 comments
Open

Split database test into separate read and write tests #10

ottok opened this issue Oct 23, 2019 · 0 comments

Comments

@ottok
Copy link

ottok commented Oct 23, 2019

The current database test runs both read and write operations. The title however says it tests "Queries per second". This is slightly misleading maybe?

I suggest you split it into read tests and title those results are "queries per second" and into write tests where the result is titled "operations per second" or simply just "read queries" and "write queries". Most of the time WordPress is doing read queries and it makes sense to compare pure read speeds. In particular in clustered environments the read speeds can be super high while write speeds are slower due to having to wait for multiple database servers to acknowledge the write.

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

No branches or pull requests

1 participant