I am using i18nmenu node for the footer block and menu block on every page. Obviously I have a lot of caching turned on and I have a ton of modules but this one is at the top of the list. I think the default cache setting is 'per_role' - would it be better for me to change it to 'global'? Any advice for how to make the block itself have a better cache? In theory it should have a really long cache since it stays the same on every page.

Comments

drupalninja99’s picture

drupalninja99 commented

ok that might be a misnomer, bc its average time is good, it had 1 really bad response time

emclaughlin’s picture

emclaughlin commented

This is true for the install I'm working on also. It's more than double the next slowest call time. Does anyone have any insight into why this is happening?

plach’s picture

plach
he/him
Primary language Italian
Location Venezia
commented

Can you identify which is (are?) the troublesome function? IIRC the only possibile perfomance impacting operations are the queries used to retrieve the translation set IDs for each menu item, but these happen only when saving a menu item.

Another possibility that comes to my mind is that i18nmenu_node uses i18nmenu's menu tree localization routines, which obviously are expensive in terms of number of queries, when generating i18n blocks. You might want to replace the i18n blocks with the original ones and compare perfomance test results.