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 2.x branch doesn't implement any type of cache, a lot of performance is lost because of that.
Comment | File | Size | Author |
---|---|---|---|
#9 | 1820748-performance.patch | 12.27 KB | dagmar |
#5 | 1820748.5.patch | 2.01 KB | GDrupal |
#3 | 1820748.module-discover-caching.3.patch | 5.96 KB | dagmar |
#1 | 1820748.module-discover-caching.1.patch | 753 bytes | dagmar |
Comments
Comment #1
dagmarThis small patch moves the module discover dependency from build() to loadFromActiveStore. So, when stop tracking and start tracking are called, the module checking is skipped.
Comment #3
dagmarLets try with this.
Comment #5
GDrupal CreditAttribution: GDrupal commentedCache wrapper function to getAllIdentifiers()
Comment #6
GDrupal CreditAttribution: GDrupal commentedlast patch commited
Comment #7
MiSc CreditAttribution: MiSc commentedSo should this be marked as fixed?
Comment #8
GDrupal CreditAttribution: GDrupal commented@MiSc not really we are still missing a few things, the import process it's taking too long for example. We need to found more ways to improve performance. I was out of ideas yesterday, I'm doing some automated test and I will comeback to this issue with a new perspective in some point.
Comment #9
dagmarThis patch contains some random stuff + some optimizations. Some test break with this but have some nice improvements in performance.
I'll continue working on this soon.
Comment #10.0
(not verified) CreditAttribution: commentedUpdated issue summary.
Comment #11
bisonbleu CreditAttribution: bisonbleu commentedHello, what is the status for this patch. Seeing that it's been 2 years, is it still relevant? Obsolete?
Thanks for clarifying.
Update: not obsolete! See below.
Comment #12
heddnbump. this takes minutes for the gui to print on my site. not the same with features.
Comment #13
bisonbleu CreditAttribution: bisonbleu commented@dagmar, is patch in #9 or parts of it at all usable? I'm trying to deal with timeout issues, especially with permissions.
Thanks
Update: looks like it is. I'm looking into it.
Comment #14
bisonbleu CreditAttribution: bisonbleu commentedHere are a recent project's stats for which I imported Tar files using CM. The first time you see refers to a local install, the second one (after vs) is on a shared hosting installation.
Obviously, there's room for optimizations, especially for permissions. That being said, it worked and it's better than having to manually reproduce a lot of complex configurations.
Update: After applying @dagmar's patch (#9) on my local install and re-importing the Tar files.
Awesome! Sorry it took 3 years, but thanks a bunch!
Comment #16
Volker23 CreditAttribution: Volker23 commentedI'm still waiting for a drush cexp -all while i found this issue. The comments to the patch looks promising so I'll give it a try. And while I'm writing this i got an "Allowed memory size" error on my local installation, where I increased the php memory step by step, right now at 2GB. Impossible to do something like this in a production environment...
Do you have a strategy or how-to to split the configuration in parts? Is that even possible? How do i get it togehter later on prod.? As far as i can see, each export has it's own tracked.inc. How to deal with this?
Any help appreciated! Thx!
Comment #17
bisonbleu CreditAttribution: bisonbleu commentedAfter a lot of experimentation, my strategy looks like this:
Hope this helps.
Comment #18
dagmarI have another approach to improve the performance of this module. It is described here: #2876984: New maintainer required