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.
Problem/Motivation
I've got many features and over 375 enabled modules, so fairly large site. features_module_info cached item in the default cache bin is causing me issues with memcache (can't have items > 1MB in size)
[warning]
WD memcache: Spent 32.96 ms splitting 1.03 MB object into 2 pieces, cid = em_-cache-features_module_info
Proposed resolution
Move features cached items to their own bin so that I can exclude them from memcache.
Remaining tasks
User interface changes
API changes
Comment | File | Size | Author |
---|---|---|---|
#15 | features_should_have-2421127-15.patch | 2.51 KB | joelpittet |
Comments
Comment #1
joelpittetComment #3
joelpittetAdd an update hook to install the new cache
tablebin.Comment #5
joelpittetAnd of course a schema would help.
Comment #6
joelpittetComment #8
joelpittetMan I keep missing things.
Comment #9
hefox CreditAttribution: hefox commentedthe return in hook_flush_caches looks misplaced
Comment #10
joelpittet@hefox it's not I don't think... it's inside the condition:
But maybe it is ok flush that cache with all flushes always?
Comment #11
hefox CreditAttribution: hefox commentedfeatures_rebuild is where it goes and checks every features and sees if it the features has been changed. cache talble should not be inside that -- it may be disabled and then the cache will never be cleared.
Comment #12
joelpittetFair point, here's a fix.
Comment #13
joelpittetThis has been working well for me, need someone to give this a test:)
Comment #14
mpotter CreditAttribution: mpotter commentedAlso, see this: https://api.drupal.org/api/drupal/modules%21system%21system.api.php/func...
I think the update hook number needs to be 7100 rather than 7000.
Comment #15
joelpittetActually 7200 because it's on the 2.x branch no?
Here's a patch.
Comment #16
mpotter CreditAttribution: mpotter commentedThink this is good now.
Comment #17
joelpittetThanks @mpotter. Do you usually let another maintainer commit your RTBC'd patches as a policy or will you end up committing it? Just curious as I just started maintaining a few projects.
Comment #18
mpotter CreditAttribution: mpotter commentedUsually it's me or hefox committing patches these days. As you can probably tell from the activity in the issue queue I'm getting ready for a release soon at which point any RTBC patch is usually committed.
Comment #19
mpotter CreditAttribution: mpotter commentedCommitted to 25b6385.