Drupal Performance Tip – replace views blocks with vanilla blocks
- Drupal Performance Tip – “I’m too young to die” – indexes and SQLs
- Drupal Performance Tip – removing unused modules
- Drupal Performance Tip – replace views blocks with vanilla blocks
- Drupal Performance Tip – “I’m too young to die” – know your DB engines
- Drupal Performance Tip – be humble on hook_init()
In the spirit of the computer video game Doom and its skill levels, we’ll review a few ways you can improve your Drupal speed performance and optimize for better results and server response time. These tips that we’ll cover may be at times specific to Drupal 6 versions, although you can always learn the best practices from these examples and apply them on your own code base.
Doom skill levels: (easiest first)
1. I’m too young to die
2. Hey, not too rough
3. Hurt me plenty
This post is rated “I’m too young too die” difficulty level.
When we start out building Drupal websites, we gradually build functionality and a common use case is creating a view, then you might want to create some blocks, very much related to the view, so you create a block view using the Views module. Then you maybe combine it with Panels or Context, it doesn’t really matter, but essentially you’ve been using the UI tools which are for ease of use, and the overhead for that lies in quite a bit of abstraction layer which later may cost in performance. Replacing the quicklinks and help and support blocks that were used in our theme’s sidebar from being a view based block to a simple programmatiaclly created block implementation proved to reduce a sizzling amount of ~200ms to ~2ms of server time spent on doing the same operation. That accounted for about ~200ms of page load time redduction for each page load, as this item was featured in many pages consistently on our theme.