-
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
Number of items in category maxed out at 10000 on front end. #12432
Comments
More often than I'm comfortable admitting, I feel like the Magento team develops their code under the assumption that just a couple people with very few wants will ever browse a site at any given time. This is the feeling you get when reading through so many of the tickets here. So many of the problems just scream complete lack of planning for scale. |
Magento is designed with performance and scaling in mind indeed. See #8477 (comment) for more details behind such decision. You can change default Please get back to here with feedback if it worked or not. |
Changing the value in the |
@orlangur Like #9498 or the countless indexing issues listed here that rear their heads when you have hundreds of thousands of products? Who designs a system to fail catastrophically and without any error messages, or ways to resume progress, when dealing with several-hours-long processes? People who don't write with scale in mind. The test data you guys use should have hundreds of thousands of products. Then, and only then, will you understand the frustration that many of the big store developers experience. |
@danemacmillan sorry, I don't have to get familiar in deep with the issue you mentioned, Magento is tested with hundreds of thousands of products in fact: https://github.com/magento/magento2/blob/2.2-develop/setup/performance-toolkit/profiles/ce/extra_large.xml#L14 There always could be some special circumstances, like 10000 variations assigned to the same configurable product or something, each such situation should be reported separately in order to be investigated. |
Preconditions
Magento 2.1.8 with PHP 7.0
Steps to reproduce
Expected result
Actual result
Frontend :
Admin
The text was updated successfully, but these errors were encountered: