You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently @pimeys did some initial benchmarking of the major the code changes related to the AUMFIDARR project. This yielded some first very good insights into the impact of those changes. I think we should invest more into this testing setup to also understand the following aspects:
We should benchmark how the resolving of many to many relations changed. (the initial testing did not have a test for this imo)
We should benchmark how the resolving of one to many relations behaves depending on which side of the relation is traversed. We have different slightly code paths for each side. E.g. we should benchmark retrieving all posts for a given blog but we should also measure retrieving the related blog for a given post. (the original testing only executed one side imo)
For all queries we should generally measure the impact on the CPU load of database and query engine. My expectation is that the database shows less CPU load with the new appraoch since we moved joining logic from the db to the query engine.
We should benchmark the performance impact of pagination. Specifically we should not only measure top level pagination but also nested pagination as those have very different work profiles.
The text was updated successfully, but these errors were encountered:
I don't really trust these measurements and I don't see a point of really measuring this. Yes, we do less cpu in the db, but what matters to our users is how fast we can query.
This was removed due to us comparing ourselves to Hasura, which doesn't have nested pagination. We can add it back.
Recently @pimeys did some initial benchmarking of the major the code changes related to the AUMFIDARR project. This yielded some first very good insights into the impact of those changes. I think we should invest more into this testing setup to also understand the following aspects:
The text was updated successfully, but these errors were encountered: