Changes between Version 3 and Version 4 of Ticket #26946, comment 12
- Timestamp:
- 01/27/2014 03:26:34 AM (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #26946, comment 12
v3 v4 17 17 Agreed in general, but not for this use-case. Menus model to an object and lists of other objects better than they model to database tables, and an object structure containing everything you'd want to know about a Menu takes a lot of code and SQL queries to load up, ever page load. 18 18 19 Menus are updated very infrequently, so another 100 milliseconds to update a menu is not going to be noticed by anyone who is not being pedantic. OTOH, loading menus from the current table structure takes a lot more time and page load time for the user on ever page loadis what should be optimized, not how long it takes to update something that is likely updated less than 0.01% of the time it is online and available for visitors to access pages.19 Menus are updated very infrequently, so another 100 milliseconds to update a menu is not going to be noticed by anyone who is not being pedantic. OTOH, loading menus from the current table structure takes a lot more time during page load and that affects users and google rankings; that is what should be optimized, not how long it takes to update something that is likely updated less than 0.01% of the time it is online and available for visitors to access pages. 20 20 21 21 > (2) Serialized content can't be queried and filtered inside the DB layer.