Posted by tky on November 28, 2010 at 5:41pm
Hi, everyone
After upgraded the Hierarchical Select module to 6.x.3.6, I found out it would produce huge cache data in mysql table(1.3G!) and decrease the server performance.
It seems a big issue:http://drupal.org/node/920588
I disable this module now. But I need something similar in my site; it has complex hierarchical taxonomy.
Any suggestion?
Comments
K.I.S.S.?
Before we look at more sophisticated operations on a buggy release, can you the degrade the module back to 6.x.3.5 until this issue is resolved?
(Note: Please don't "just" degrade; if the release modified how hs accesses the database you can run into trouble. Test it on a production server and check the php and mysql errors log after running a through HS scenarios)
Hi, Kyle I tried to uninstall
Hi, Kyle
I tried to uninstall the 3.x.3.6 version and reinstall the 6.x.3.5 in my productive site. But it seems still has the same bug: 1.2G cache in past 12 hours.
I enabled these modules:
Hierarchical Select Flat List
Hierarchical Select Taxonomy Views
Hierarchical Select Taxonomy
Hierarchical Select
Now I think I really need a alternative way to implement the same function, otherwise my site would keep decreasing it's performance.
Kevin
Hmmmm...
Wait a minute... I thought the 3.6 upgrade introduced the problem? 1.2G cache table in under 12 hours /is/ ridiculous and yes you must address it. Again, be sure to do so only perform this troubleshooting on a site backup, not the live site.
Just curious, did you trunc that table prior to the 3.5 downgrade?
If you must stick with 3.6, there were a couple of options listed in that thread which you can apply as a work-around until the maintainer identifies and distributes a patch. #19 has an attached patch, but that merely truncs that table on every cron run. So you could run the patch and adjust your cron to a more aggressive frequency.
Alternative?
Did you find an alternative for Hierarchical Select? We've got a problem wit hit also (http://drupal.org/node/1006094) and need to find a solution..
Regards,
Jeffrey