

New WAMP stack: min 399ms, median 483ms, max 539ms.Old notebook: min 1201ms, median 1261ms, max 1357ms.New LAMP stack (in VirtualBox): min 1410ms, median 3659ms, max 5045msĪnd the same test with concurrency set to 1 (instead of 10):.New WAMP stack: min 367ms, median 675ms, max 1893ms.Old notebook: min 1201ms, median 1734ms, max 3728ms.

10 concurrent threads, 100 iterations were used for the benchmark. The test consists of connecting to a database and reading a single record form a table using INNER JOIN on 3 more (indexed) tables, repeated 100 times within a loop. What the hell? The new LAMP performed miserably, and even the new native WAMP was outperformed by the old notebook.

Old notebook: min 0ms, median 39ms, max 218ms.Again, 10 concurrent threads, 500 iterations were used for the benchmark. The PHP runs a loop of 1000 and generates sha1(uniqid()) inisde. Right here I don't get why the native WAMP stack performed so bad, but at least the LAMP environment brought the expected speed.Īpache performance measurement for non-cached PHP content. New LAMP stack (in VirtualBox): min 6ms, median 46ms, max 175ms.New WAMP stack: min 71ms, median 135ms, max 296ms.Old notebook: min 47ms, median 111ms, max 156ms.Started Apache performance benchmarking with Apache Benchmark for a small static HTML file (10 concurrent threads, 500 iterations). Disc specific tests showed that read/write operations peaked around 380M/160M for the SSD, and all the different sized block operations also performed very well. I started to do a lot of benchmarking and profiling, and here is what I've found:Īll general benchmarks (Performance Test 7.0, HDTune Pro, wPrime2 and some more) gave a big advantage to the new notebook. Apache, PHP and MySQL configurations were practically identical in all environments. And here came the nasty surprise, one of those projects produced a lot worse response times than on my old notebook (that was true for both the VirtualBox and WAMP stack). This still all worked great out, then I started to pull in my projects to these stacks.

Then I started to build up my development stack, both as LAMP (using VirtualBox with a Debian guest) and WAMP (Windows native Apache + MySQL + PHP). My initial experience was what I expected, fast boot, quick load of all the applications (Eclipse now takes 5 seconds as opposed to 30 seconds on my old notebook), overall great experience. I just switched from a Core2 Duo Vista 32-bit notebook with 2GB RAM and SATA HDD, to an i5-2520M Windows 7 64-bit with 4GB RAM and 128 GB SSD (Corsair P3 128). I'm a web application developer using my notebook as a standalone development environment (WAMP stack).
