Quicktabs can sure use more caching
For Drupal, Quicktabs is a useful module that provides helpful user navigation aids for a site. Used properly, it can be of great assistance to users navigating your site.
We mentioned in a previous article that certain settings can be detrimental to performance, for example, when you load all 3 tabs at once, in anticipation of the user navigating to them later. If the underlying blocks or views involve heavy queries, then the page loading can triple, and server load can suffer. We submitted a patch that warns the user that such a settings can have drawbacks. It has been accepted and is now part of the standard module.
We faced another case recently that involved quicktabs dragging performance down for a client site. They have several blocks that are visible on all pages, each with many tabs. All of those tabs were based on views, which were inherently heavy because of what they have to do.
Neither views caching nor Drupal core's block caching helped here.
The solution was to patch quicktabs to make it do its own caching of views. The patch is in the issue queue for quicktabs at
To assess the impact of with and without the patch scenarios, here are some pretty graphs:
Applying the patch made the site go back to normal again.
Is your Drupal site slow?