Benchmarking Drupal
Sure, Benchmarks have their drawbacks. But they are very useful for certain types of testing. For example we can do a standard stresstest on the latest stable version of Drupal versus CVS and see where we have to gain speedwise. Or see the influence of modules and or themes on the speed of Drupal. And we can use it as well "against" other CMS'es.
Lets first come up with a standard scenario for testing that can be ported in time an place on different hardware and OS. Once we have established that we must make some decisions on standard ways of reporting and how to communicate to whom. Some reports might be for the developers, others for marketing.
BTW: if you don’t see two dolphins jumping out of the water, you are a bit stressed yourself and should consider helping out here. So how about it, do /you/ want to join?
Are performance optimisations still going into D6?
I'm assuming it's too late, but if not here's an easy performance win for D6:
<
blockquote>The type column of the {system} table is currently a varchar(255) field. Yet in 99% of all Drupal installations it stores either the text 'module' or the text 'theme' and nothing else. This is already a strong case for making it an int column and defining constants for module and theme. Then, on every page, there is this query:
SELECT filename FROM system WHERE name = 'user' AND type = 'module';
Are you storing your Drupal sites or configs in a version control system? If so, which?
Presentation: Drupal performance tuning and optimization
OpenCraft hosted a 3.5 hour seminar that I presented on Drupal performance tuning and optimization. You can find the slides from the presentation there, which can be useful to some of you.
Drupal memory consumption by core and modules
I create a 5.2 and 6.x patch for measuring how much memory a module takes, and also how much the whole Drupal page load takes.
The results are published here: Measuring memory consumption by Drupal bootstrap and modules.
Short version: in Drupal 6, modules are better off than in 5.2, but the bootstrap is a tad larger.
If anyone is interested in replicating the results with more realistic install profiles, please do so and publish your results/findings/recommendations.
Convenient SQL transactions with PressFlow Transaction
I've released an in-development version of PressFlow Transaction for developers interested in convenient encapsulation of SQL transactions. The key features are intelligent use of scope for COMMITs and ROLLBACKs as well as safe, intelligent nesting of transactions to get exception-like semantics.
Usage details are on the project page. Requires PHP 5.
(I posted this to the High-Performance group because encapsulating updates in transactions can dramatically improve performance.)
SoC 2007 proposal - Drupal Automated Staging Kit
Hello all,
Sorry for cross-posting; but I think people working on different aspects of Drupal may have interest in this idea.
I've submitted a SoC 2007 Drupal proposal on automating the whole process of creating a complete Drupal site with a LAMP stack in a self-contained virtual machine image. A formatted PDF version is here:
http://www.abeharry.info/SoC2007_DrupalAST_FullProposal.pdf
Here is the abstract:
The Drupal automated staging toolkit is a proposed set of code libraries, file schemas and parsers, and code generators, for
New caching module for complex and high-load sites
I've just released two modules for developers and maintainers of performance-intensive sites. The first module provides a new, self-tuning, preemptive cache API for modules. It's called PressFlow Preempt. The second module (named PressFlow Preempt Panels) builds on the first by seamlessly offering cached versions of Panels.
Building a Drupal benchmarking test suite
Hi there, I have some interest in building a Drupal becnhmarking suite that can be used for testing the impact of newly proposed patches on our beloved content managemanet framework.
Benchmarking drupal.org upgrade
One thing I would be really interested in seeing is a benchmark suite run on the current drupal.org installation, and then again once it's upgraded to 5.0. Is this something that could be done or is being planned? It would be an underestimate of performance gains to the extent that certain performance patches are applied directly to d.o when fixed in core.
Performance upgrades from the CHANGELOG include:
Graphing out watts used with Drupal
Inspired by Dries posting on the powersavings one can get by having a system run on low CPU usage:
Say we would make a test with 1k nodes in Drupal and Joomla? and run JMeter with the same parameters on it against both. Both would be optimzed for caching.
It would be nice to make some MRTG/RRD stats on it with using the MIBS of Watts used and CPU's cycles burned. Then we can show that Drupal will burn less cycles and is in fact environmental friendlier then Joomla?.
Some initial documentation
I made an attempt at starting some documentation around benchmarking code:
Reviews/Additions would be appreciated. :)
excellent idea - some starting points
I've posted on standard benchmarking information before (with no responses...) in the performance and scalability forum which is a pretty good source of information in general.
Sure, Benchmarks have their drawbacks. But they are very useful for certain types of testing. For example we can do a standard stresstest on the latest stable version of Drupal versus CVS and see where we have to gain speedwise. Or see the influence of modules and or themes on the speed of Drupal. And we can use it as well "against" other CMS'es.
Lets first come up with a standard scenario for testing that can be ported in time an place on different hardware and OS. Once we have established that we must make some decisions on standard ways of reporting and how to communicate to whom. Some reports might be for the developers, others for marketing.
BTW: if you don’t see two dolphins jumping out of the water, you are a bit stressed yourself and should consider helping out here. So how about it, do /you/ want to join?
