Calling Developers!
We are reenergizing our code contribution process! Learn More

Known memory leak problems with propel 1.x?

Options
U0234H88AJG
U0234H88AJG Posts: 2 🧑🏻‍🚀 - Cadet
edited June 2023 in Propel ORM

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?

Tagged:

Best Answer

  • Alberto Reyer
    Alberto Reyer Lead Spryker Solution Architect / Technical Director Posts: 690 🪐 - Explorer
    Answer ✓
    Options

    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

Answers

  • Alberto Reyer
    Alberto Reyer Lead Spryker Solution Architect / Technical Director Posts: 690 🪐 - Explorer
    Answer ✓
    Options

    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

  • U0234H88AJG
    U0234H88AJG Posts: 2 🧑🏻‍🚀 - Cadet
    Options

    Thank you for your feedback. 🙏