Intent: Characterize Drupal Performance Improvements with PECL Alernative PHP Cache
| Hardware Used | Sun Fire X2100 server; 1x2.2GHz dual-core Opteron; 4GB memory |
|---|---|
| Drupal Version | Drupal 5.3 |
| Drupal Database | 2000 users, 5000 nodes, 10000 comments, 250 vocabulary items; 15 vocabularies (generated with Drupal 'devel/generator' module) |
| Alternative PHP Cache Enabled | PECL APC 3.0.15 |
| Load Generator | Faban 'fhb' 0.9 (check it out!) |
| Nature of Workload | Concurrent hits against font page (not logged in) |
| SAMP | LAMP | |
|---|---|---|
| Operating System | Solaris 10u4 (within non-global zone) |
SLES 10.1 |
| AMP Stack | Coolstack 1.1: Apache 2.2.3 MySQL 5.0.33 (32-bit) PHP 5.2.0 |
Bundled AMP: Apache 2.2.3 MySQL 5.0.26 (64-bit) PHP 5.1.2 |
| Observed ops/sec improvement | -0.5% to 5.3% | -8.5% to 46.7% |
Commentary:
- Results at this point are only an indication - shouldn't be used for comparison yet - need more realistic workload
- If you're using LAMP on Sun, definitely install PECL APC for an immediate performance improvement
- As Coolstack is optimized for Solaris, and Solaris for Sun Fire servers, it is not surprising that SAMP is better tuned 'out of the box'
- Results reported only for workloads that do not produce '503' errors (overloaded server)
Sign up or Log in to add a comment or watch this page.