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
Enhance aggregator REST API performances #1327
Comments
We did some performances tests prior and after the apply of the patch. Before the patch
After the patch
|
Using the direct conversion between database records and messages, the performances are the following:
80% of the requests are served in less than 943ms instead of 1941ms. The RpS is > 110 instead of >60. |
After the last patch, the signed entities routes have been tested with the following performances:
All routes performances are now acceptable. |
Why
The REST API of the aggregator performances are sub-optimal and have led to some unreachability as seen in #1310.
What
We want to have better performances of the aggregator by implementing long term solutions such as:
How
fn get_database_records<R: From<DatabaseRecord>>() -> StdResult<Vec<R>>
function with a generic type)Certificate
SignedEntity
WAL
, use pragmaPRAGMA journal_mode=WAL;
and make sure that the current SQlite crate used is compatible)Later
tower
which is compatible withwarp
)LIMIT
in providersThe text was updated successfully, but these errors were encountered: