-
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
Grid Massaction Bandwidth Usage of setGridIds #47
Comments
@amenk For now, the issue is not scheduled for implementation. However, there are two related technical tracks: backend grids extendability & modularity, and performance. You will be notified, as soon as there is any activity on the internal ticket. |
Closing the ticket for now, it will be reopened upon an activity on the corresponding internal ticket. |
[MPI] Optimization and bug fixes
[Vanilla] Bug Fixes. P1. JS static fails
* MC-42052: Fix jQuery.fn.click() * MC-42052: Replace jQuery click shorthand function Co-authored-by: Sergii Ivashchenko <serg.ivashchenko@gmail.com>
If a grid supports massaction / select all, all the ids of all pages of a grid are included in the page in the setGridIds call (see Mage_Backend_Block_Widget_Grid_Massaction_Abstract). If the shop has for example 10000 products this is around 50 KB of data that is included on every page of the product listing.
To improve performance, the currently included grid IDs could be stored in the session server-side and the mass action select all could reference to this session storage for example by an unique hash.
The text was updated successfully, but these errors were encountered: