-
Notifications
You must be signed in to change notification settings - Fork 69
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
Investigate and fix throughput issues related to read only transactions and HTTP #1662
Comments
heifner
added a commit
that referenced
this issue
Sep 27, 2023
PH: Add a longer running read-only trx for tests
heifner
added a commit
that referenced
this issue
Sep 30, 2023
heifner
added a commit
that referenced
this issue
Oct 2, 2023
heifner
added a commit
that referenced
this issue
Oct 2, 2023
heifner
added a commit
that referenced
this issue
Oct 4, 2023
… so that application is created on the main thread.
heifner
added a commit
that referenced
this issue
Oct 4, 2023
heifner
added a commit
that referenced
this issue
Oct 4, 2023
heifner
added a commit
that referenced
this issue
Oct 4, 2023
Reduce the number of thread hops for read-only trxs
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
Initial performance testing of read only transactions indicated read-only transactions are not reaching peak throughput. This issues focuses on the C/C++ code for leap and enabling peak throughput.
Related Issues
Performance testing code and the performance testing harness are covered by #1634
The text was updated successfully, but these errors were encountered: