You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
The text was updated successfully, but these errors were encountered:
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.
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!
The text was updated successfully, but these errors were encountered: