Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
I noticed a huge performance drop in a site that I run, after me and my colleagues digged into the cause we found that the filefield widget array in _content_type_info() contained over 260,000+ blank items. This was then repeated another 2 times in the cache blob.
What could cause all these extra array items? It's causing a huge performance loss and out of memory errors when drupal tries to unserialise the content.
We posted here http://drupal.org/node/1009596 and narrowed it down to filefield.
Any help would be great.
Comments
Comment #1
quicksketchI got another issue over in the Insert queue: #1091648: Performance issues - unusual huge mysql row size, unusual huge memory and cpu usage. It doesn't seem like any issue has quite discovered what the actual source of this problem is, though #1009596: _content_type_info() memory usage improvements seems a bit more on track. Do you also have Insert module installed?
Comment #2
buddaAny idea what these empty widget array items are actually for? (as seen in http://dl.dropbox.com/u/1286874/debug.txt output)
Comment #3
buddaThe Insert module isn't installed on the problematic site.
Only related modules (I think) are: ImageField, FileField Paths.
Comment #4
mikebell_ CreditAttribution: mikebell_ commentedDisabling Imagefield and FileField Paths doesn't solve the issue unfortunately.
Comment #5
lpalgarvio CreditAttribution: lpalgarvio commented+1
got the same issue with insert module.
Comment #6
buddaIs there any good place to start in debugging this problem? Happy to get stuck in, but if anyone knows the best place to start to save time I'm all ears.
Comment #7
apadernoComment #8
lpalgarvio CreditAttribution: lpalgarvio commentedthis issue is very serious.
http://drupal.org/node/1091648
Comment #9
quicksketchYes, very serious but I still have no idea how to recreate the problem and I'm not seeing it on any of my sites.
Comment #10
apadernoI am closing this issue, which is for a not supported Drupal version.