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.
Calling module_implements loads up files. We don't want to do this. Thus this needs to be cached.
Comment | File | Size | Author |
---|---|---|---|
#4 | advagg-1996828-4-add-in-full-cache.patch | 7.2 KB | mikeytown2 |
#1 | advagg-1996828-1-cache-module-implements.patch | 863 bytes | mikeytown2 |
Comments
Comment #1
mikeytown2 CreditAttribution: mikeytown2 commentedShaves ~10ms off of the request for an advagg cache hit. Following patch has been committed
Comment #2
mikeytown2 CreditAttribution: mikeytown2 commentedI've gotten this down to
core: 7ms, advagg: 9ms
using microtime(TRUE) timers. Using xdebug it showscore: 32ms, advagg: 42ms
. ~30% slower when we are talking about 2ms isn't a big issue in my opinion. If I wanted to get more out of it I could cache advagg_merge_plans or _advagg_aggregate_css/js but that would give me a lower cache hit ratio for that cache due to inlined output. Nonetheless something to think about.Comment #3
mikeytown2 CreditAttribution: mikeytown2 commentedBy adding caching at the highest level I got this to be faster than core.
microtime: 4ms
xdebug: 17ms
I'll build a setting to turn caching on and off.
Comment #4
mikeytown2 CreditAttribution: mikeytown2 commentedThe following patch has been committed.