Did anyone experienced such a magic in Propel when P&S happens?
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 ofvendor/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.
Comments
-
Thanks Janis, we will investigate this.
0
Categories
- All Categories
- 42 Getting Started & Guidelines
- 7 Getting Started in the Community
- 8 Additional Resources
- 7 Community Ideas and Feedback
- 75 Spryker News
- 924 Developer Corner
- 783 Spryker Development
- 88 Spryker Dev Environment
- 362 Spryker Releases
- 3 Oryx frontend framework
- 35 Propel ORM
- 68 Community Projects
- 3 Community Ideation Board
- 30 Hackathon
- 3 PHP Bridge
- 6 Gacela Project
- 25 Job Opportunities
- 3.2K 📜 Slack Archives
- 116 Academy
- 5 Business Users
- 370 Docker
- 551 Slack General
- 2K Help
- 75 Knowledge Sharing
- 6 Random Stuff
- 4 Code Testing
- 32 Product & Business Questions
- 70 Spryker Safari Questions
- 50 Random