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
We wanted to have a discount store-wide - with over 20k products. We created a price list with all the products in it. I was able to see the money_amounts and the price list was there in the database. But as soon as we go in the price list table in the admin panel, it seems like all product information is fetched therefore creating a really huge query resulting in a time out - and as node is single thread - it hangs the backend until we manually restart the backend or the query finishes.
System information
Medusa version (including plugins): 12.1
Database: Postgres
Operating system: Linux
Steps to reproduce the behavior
Create a parice list
Add more than 10k products
Click in Price List on the admin panel
Backend becomes unresponsive
Expected behavior
I need to have a more in-depth look at why this happens, but I would expect us to be able to do big price lists without having to worry about crashing the store/backend.
The text was updated successfully, but these errors were encountered:
Bug report
Describe the bug
We wanted to have a discount store-wide - with over 20k products. We created a price list with all the products in it. I was able to see the money_amounts and the price list was there in the database. But as soon as we go in the price list table in the admin panel, it seems like all product information is fetched therefore creating a really huge query resulting in a time out - and as node is single thread - it hangs the backend until we manually restart the backend or the query finishes.
System information
Medusa version (including plugins): 12.1
Database: Postgres
Operating system: Linux
Steps to reproduce the behavior
Expected behavior
I need to have a more in-depth look at why this happens, but I would expect us to be able to do big price lists without having to worry about crashing the store/backend.
The text was updated successfully, but these errors were encountered: