Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Saving multiple objects in a loop is extremely slow #82

Open
jantomicky opened this issue Jul 13, 2020 · 3 comments
Open

Saving multiple objects in a loop is extremely slow #82

jantomicky opened this issue Jul 13, 2020 · 3 comments

Comments

@jantomicky
Copy link

In our project, we have several console commands that modify lots of Pimcore objects (products), in a loop (synchronization of external data to Pimcore). These are called with CRON.

When we set up the connector / bridge, these commands basically slow down to the point of not working (think ~50 processed objects over 20 hours, whereas when we unpublish the connector configuration, we are able to process tens of thousands in about 4 hours).

Could this be related to #63 in any way? Is there a way of temporarily disabling the connector for specific actions, for the duration of the process (unregistering the event listeners, maybe)?

Will #41 with version 2.0 solve this, and if so, when will it be out, and can we help somehow? Thanks!

@mbolka
Copy link
Contributor

mbolka commented Jul 16, 2020

Hi @jantomicky,
Version 2.0 will be available the next month (we aim towards 2'nd - 3'rd week in August). It will have a built-in system of rules when you want to synchronize your products, which can be easily extended. You can write your custom rules (for ex. listen for a specific env value) and then use them to prevent the connector from updating during import/export and call mass export after it is finished.
#63 Is almost done for the version 2.0, so you should see a big improvement. Keep in mind that sync performance heavily depends on your network performance and latency between Pimcore and Magento servers.

@jantomicky
Copy link
Author

Awesome, thank you very much!

@agendartobias
Copy link

We have the same problem. But problem only exists if we have pimcore enviroment set to PROD mode. If enviroment is set to DEV mode savings are fast.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants