The KernelTrap pages are managed by Drupal, a modular content management engine written in PHP with a MySQL backend. The site is hosted on a Linux server running Apache.
I am on the verge of writing a new site and I was going to use Joomla, but like the look of this site. I note that Drupal have just launched a new version of their CMS - is Kernel trap on the old version or the new version and do you know what the differences are, if you are on the old version?
There are multiple levels of caches. We're using MySQL's query cache. And APC as an op-code cache. And Drupal's caching layer (most beneficial for non-logged-in users such as yourself), tuned to enforce a minimum cache lifetime of 5 minutes. Custom code is constantly being evaluated for performance, with poorly performing queries optimized.
I need to set up a DB slave some time soon, as our regular backups cause problems when the mailarchives get busy. Actually, the mailarchive software can stand to be optimized quite a bit more utilizing the Drupal caching layer for expensive queries (ie "subject LIKE '%...%'" across our entire lkml archive...)
Which version of Drupal?
I am on the verge of writing a new site and I was going to use Joomla, but like the look of this site. I note that Drupal have just launched a new version of their CMS - is Kernel trap on the old version or the new version and do you know what the differences are, if you are on the old version?
4.7
KernelTrap is currently using Drupal 4.7. Find more information about Drupal 5.0 here.
5
KernelTrap is now using Drupal 5.
How so fast?
I'm impressed with the speed of the site. What kind of cache-ing is used? Apache? PHP op-code? which one?
Caches
There are multiple levels of caches. We're using MySQL's query cache. And APC as an op-code cache. And Drupal's caching layer (most beneficial for non-logged-in users such as yourself), tuned to enforce a minimum cache lifetime of 5 minutes. Custom code is constantly being evaluated for performance, with poorly performing queries optimized.
I need to set up a DB slave some time soon, as our regular backups cause problems when the mailarchives get busy. Actually, the mailarchive software can stand to be optimized quite a bit more utilizing the Drupal caching layer for expensive queries (ie "subject LIKE '%...%'" across our entire lkml archive...)