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
{{ message }}
This repository was archived by the owner on May 29, 2019. It is now read-only.
As a Magento developer, I would like the Catalog Bulk API endpoints on Save to be optimized so that bulk Save operations execute as quickly as possible.
Currently many different actions are performed by Magento as a result of a product save. One example of such action is generating url rewrites (which executes as a blocking call) if they're needed. The idea is to analyze each step and see if we can save execution time by performing some of these actions at different times - like executing all url rewrite logic after the products have otherwise been saved. Can we save time by moving these around instead of executing product Save calls back-to-back-to-back in their current form?
High level tasks:
Investigate url rewrite generation and provide a recommendation on how to handle them in a bulk product save API call
Investigate what other steps in the product save operation can be moved around to save on execution time (do we have any other examples?)
The text was updated successfully, but these errors were encountered:
misha-kotov
changed the title
Performance optimizations on Save
Performance optimizations on Save for Bulk products endpoint
Dec 4, 2017
As a Magento developer, I would like the Catalog Bulk API endpoints on Save to be optimized so that bulk Save operations execute as quickly as possible.
Currently many different actions are performed by Magento as a result of a product save. One example of such action is generating url rewrites (which executes as a blocking call) if they're needed. The idea is to analyze each step and see if we can save execution time by performing some of these actions at different times - like executing all url rewrite logic after the products have otherwise been saved. Can we save time by moving these around instead of executing product Save calls back-to-back-to-back in their current form?
High level tasks:
The text was updated successfully, but these errors were encountered: