Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
The render cache (level 3 currently), seems to be fairly safe. Doing some analysis of the advagg code and the hook_js_alter & hook_css_alter are a big slow point. So I'm thinking I'll want to bring back this level of caching; luckily the difference won't be as dramatic; but it will cut down the time in half based on some of my initial tests.
Comment | File | Size | Author |
---|---|---|---|
#5 | advagg-2458871-5-cache-hook-alter.patch | 7.78 KB | mikeytown2 |
#4 | advagg-2458871-2-bring-back-dead-code.patch | 9.55 KB | mikeytown2 |
#1 | advagg-2458871-1-cache-level-5.patch | 11.89 KB | mikeytown2 |
Comments
Comment #1
mikeytown2 CreditAttribution: mikeytown2 commentedPart 1 done. Added in a cache level of 5; not on the admin page yet.
Comment #4
mikeytown2 CreditAttribution: mikeytown2 commented2nd part done. Will need to think more about hook_advagg_current_hooks_hash_array_alter & the cache level being used.
This is slated for release in the 2.9 version. Wanted to get some of this back in place so the speed of 2.7 can be achieved in 2.8 even if we're only talking about a 5-15 ms difference.
Also blocked on this #2453579: Investigate aggressive cache & defaultCommentAttribution. Need to make sure this is working before moving the aggressive cache to normal and creating a new aggressive cache level
Comment #5
mikeytown2 CreditAttribution: mikeytown2 commentedCommitted this as it will help to mitigate #2469063: locale_js_alter() - PDOException: Integrity constraint violation: 1062 Duplicate entry 'javascript_parsed'