-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Surcharges slow down order retrieval #3225
Comments
As additional info: The same customer also created an order with 30 surcharges and 63 order lines. The server ends up running into a memory heap allocation error and crashes. Note that our production uses postgres and the reproducible uses sqlite so that could also be a major factor why our production is this much slower but even with sqlite it's a significant slow down on an otherwise vanilla vendure instance. |
Thanks for this detailed report. Right now I have no idea why this performs in this way. Definitely needs some thorough further investigation. |
Describe the bug
Adding many surcharges to an order makes the retrieval of the order (with surcharges) significantly slower.
To Reproduce
Steps to reproduce the behavior:
addSurchargeToOrder
graphql mutation 60 times to add 60 simple dummy surchargesOrderDetailQuery
(~200ms)OrderDetailQuery
without surcharges onOrder
typeOrderDetailQuery
(~25ms)Expected behavior
The surcharges should not impact query time on the Order
Environment (please complete the following information):
Additional context
Full reproducible
The text was updated successfully, but these errors were encountered: