Did anyone experienced such a magic in Propel when P&S happens?

UNBSW8S8K

Hello!

Did anyone experienced such a magic in Propel when P&S happens? It propagates propel quite a lot with redundant joins, columns e.t.c. This is causing huge memory usage for queue:task:start event. It comes from core of
vendor/spryker/product-page-search/src/Spryker/Zed/ProductPageSearch/Persistence/ProductPageSearchQueryContainer.php:151 in scenario when there is one message failing from processing batch. Package version is latest - 3.9.1.

1st image is after 6 iterations. 2nd image - 3rd iteration. There is huge difference in columns. Same thing happens to joins and everything else, that is called more than once on query builder.

Valerii Trots

Thanks Janis, we will investigate this.