Known memory leak problems with propel 1.x?
Does anyone experience or know about memory leak problems with propel 1.x when handling large amounts of complex join queries during data synchronisation? How do you address these problems? Is it useful to disable the Propel cache using disableInstancePooling() during data export?
Best Answer
-
The issues are not the joins, but loading a lot of different entities that are kept in the instance pool. You might face the issue because every joined entity/table will make the usage of the instance cache even worse.
So yes we have deactivated the instance pooling for exports / imports that interact with a lot of entities in a single process.
Just use\Propel\Runtime\Propel::disableInstancePooling()
at the beginning of your process
0
Answers
-
The issues are not the joins, but loading a lot of different entities that are kept in the instance pool. You might face the issue because every joined entity/table will make the usage of the instance cache even worse.
So yes we have deactivated the instance pooling for exports / imports that interact with a lot of entities in a single process.
Just use\Propel\Runtime\Propel::disableInstancePooling()
at the beginning of your process
0 -
Thank you for your feedback. π
0
Categories
- All Categories
- 42 Getting Started & Guidelines
- 7 Getting Started in the Community
- 8 Additional Resources
- 7 Community Ideas and Feedback
- 69 Spryker News
- 899 Developer Corner
- 760 Spryker Development
- 83 Spryker Dev Environment
- 361 Spryker Releases
- 3 Oryx frontend framework
- 34 Propel ORM
- 68 Community Projects
- 3 Community Ideation Board
- 30 Hackathon
- 3 PHP Bridge
- 6 Gacela Project
- 24 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
- 68 Spryker Safari Questions
- 50 Random