magento / magento/catalog-storefront
Measure current state of Export API
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 7
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
Parent: #227
Ned to discover existing bottle-necks with Export API
Profile:
- magento2ce/setup/performance-toolkit/profiles/ee/medium_msite.xml
Repos:
- Magento 2 EE
- https://github.com/magento-commerce/commerce-data-export
- https://github.com/magento/catalog-storefront
AC:
- time and memory consumption should be measured
- measure the independent time of full reindex for product/category/variation feed used by Export API
- measure full sync time of uploading data to Storefront
Test protocol should be provided:
- steps to reproduce (scripts attached if any used for testing)
- used environment (cores, memory)
- commits
Note: for docker-based installation avoid sync between host and guest machines (do code copy to the container directly)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with magento2ce/setup/performance-toolkit/profiles/ee/medium_msite.xml and review the commerce-data-export and catalog-storefront repositories. Establish the environment and commits used, then measure memory and time for the product, category, and variation feed reindexing and the full Storefront sync. Done means the measurements and reproducible protocol, including setup steps and any scripts, are recorded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend-api-design, performance
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100