-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Removing 85.000 products from backend takes 28 hours! #1823
Comments
First of all, better to use indexation on schedule for this case. |
Use import functionality for mass delete? We don't really care import takes this long, it's the initial load.. |
@rklerck hi, can you please confirm that you use "reindex on schedule" for all the indexers related to catalog? |
Tried that, ended up with #1833 |
@choukalos Chuck--i see your reference to a closed issue. Can you take a look at this one and reassign as needed? |
Hi @rklerck What version of Magento are you using? Thanks, |
@choukalos Then like @rklerck says Mass Delete function for me i have let run for 3 days to delete over 85k products at once because they imported and had missing data causing an Segmentation Core error while indexing keywords. Magmi for 1.92 was amazing at importing/updating products but this isn't an option for magento 2.x to compare to what ever @rklerck server is mine is. result = magento 2.x needs Magmi style import/update/delete system. |
Thank you for your submission. We recently made some changes to the way we process GitHub submissions to more quickly identify and respond to core code issues. Feature Requests and Improvements should now be submitted to the new Magento 2 Feature Requests and Improvements forum (see details here). We are closing this GitHub ticket and have moved your request to the new forum. |
We've added 85000 products with rest, this takes 14 hours. This seems fair because of a request for each product. But when we remove the products all at once in the backend, it takes 28 hours!!
The text was updated successfully, but these errors were encountered: