Windows Cache Extension for PHP is a PHP accelerator that is used to increase the speed of PHP applications running on Windows and Windows Server. Once the Windows Cache Extension for PHP is enabled and loaded by the PHP engine, PHP applications can take advantage of the functionality without any code modifications.

The documentation makes no mention of Apache, only IIS. I decided to give it a try, and to my amazement, WinCache worked in Apache on Windows. After that I decided to compare the performance of WinCache with the other available options for Windows+Apache.

I referenced the following sites who performed similar tests, but in IIS:

• PHP on Windows: The WinCache 1.0 Benchmark – ibuildings.com techPortal, Ivo Jansch
• WinCache – Preliminary tests look REALLY good. – Cal Evans

You can grab WinCache, and information about it, here:

• Windows Cache extension for PHP website on Microsoft.com
• The PECL repository page for WinCache
• Ruslan Yakushev’s blog posts about WinCache (WinCache Developer)

Testing Environment

• Hardware
  • AMD Athlon 64 3800+ (2.50GHz, single core)
  • 2.0GB DDR2
• Software
  • Windows Server 2003 w/ SP2
  • MySQL 5.1.40, locally installed
  • Apache 2.2.14 vc9
  • mod_fcgid 2.3.4
  • php 5.3.1 ts/nts vc9
  • WordPress 2.9.1 base install (wordpress is a good “everyman” product for simulating “real world” use, even if its code is ugly)
• OpCode Cachers
  • APC 3.1.3.0 (3.1) (NTS)
  • WinCache 1.0.1117.0 (1.0, stable) (NTS)
  • XCache 2.0.0-dev(r688) (TS)
  • eAccelerator 0.9.6rc1 (TS)

Test Method

To run an unbiased test, I tried to remove as many variables as possible. A batch script was written to perform the following (thus garaunteeing that every test was identical):

1. Stop the apache service
2. Start the apache service
3. Run ab (Apache Bench), piping output to a text file
4. Repeat 1-3 with incremented Concurrency levels (1, 3, 5, 10)
5. Notify me that all tests have been completed.

Aside from testing the relative performance of each opcode cacher, I also wanted to see how well they performaned under differnt levels of “stress”, which is why I included Step 4 with different levels of concurrency. After each test-run, I would switch out the opcode cacher in PHP.ini, making sure that the individual opcode cacher settings were “equal” in all ways possible (same amount of shared memory, etc etc). After all test-runs were completed I went through the test files that were generated and compared the results in various graphs.

To form a baseline, I also ran the test with no opcode cacher, in both TS (PHP as a module) and NTS (PHP through FastCGI) setups.

Results

The results were extremley eye-opening for me. Here is the pretty graph:

Let’s disect this graph a little bit.

• Not using an OpCode cacher, if able to, is stupid. The performance gain from using ANY of the available OpCode cachers is amazing. For that matter, any form of caching; If you aren’t caching ANYTHING, you are stupid.
• Non-Thread Safe (NTS, FastCGI) PHP performs better than Thread Safe (TS, Module) PHP. Duh.
• WinCache works in Apache. This one is obvious from the graph & my tests, but if you were to go read documentation for WinCache it strictly talks about IIS. This is great news for Apache on Windows, because WinCache is made specifically for windows – unlike the other OpCode cachers which are usually made with Linux in mind and ported to Windows as an afterthought.
• XCache’s performance increased as the “stress” increased. All other opcode cachers either performed the same accross the board or decreased in performance as the “stress” level increased. It would be interesting to run larger concurrency tests to see where XCache’s performance falls off at.
• WinCache came out as the top performing opcode cacher, on this setup, in this environment, during these tests.
• XCache and APC performed exactly opposite of each other as the “stress” increased. eAccelerator was practically the “best fit line” for XCache and APC, but it did performed slightly better when averaged across concurrency levels.
• APC performed almost as well as WinCache at the lowest (none) concurrency level.

What does this all mean?

It means that in my tests, on Windows, in Apache, using bleeding edge software, I have shown that WinCache is a viable option for Windows development and production servers. I have not shown that WinCache is THE BEST option or the ONLY option; just that is an option — regardless of what my graphs show. Why? Because benchmarks suck and they only exist to show a relative level of performance as compared to others in an isolated environment. You may have different results. You may need additional features. You may have political/fanboi issues with using one or the other. Will I be using WinCache going forward? Yes, and I will also recommend it to others.

7 Things you may not know about me:

1. I’ve been working at the same desk job since I was 15 (now 22). I was a hardware technician at first, then became the network engineer/system admin, and am now a systems developer (fancy title for programmer).
2. I have a slight obsession with collecting and passing out stickers.
3. My nickname (spoon) originates from a mock stand-up comedy routine I did during a class in Middle School. In the script, someone was insulting me with names of common household items. One of the insults was “SPOON!” Ever since then, it just stuck with me. Yes, boring, lame, I know. I used to tell people I was either obsessed with The Tick! or an ex-heroine addict.
4. I use PHP on windows, exclusively. That isn’t the shocking part. Are you ready for it? I use PHP, on windows… with Apache – exclusively. *GASP* Yes, I am one of the few, the proud, the WAMP stack users (in a production environment, no less!!!)
5. I co-own a few web properties with my Fiance, Katie Soltysiak, which include: DIYscene – Alternative Craft and Indie Design Forum, eBurl – Short, Trackable eBay URLs, OwnTheHour – Independent Etsy Promotion
6. I am scared of Linux.
7. I have a police record in the state of Wisconsin.

7 More people to add to this meme.
Now, since I am so late with getting my post written, almost everyone I can personally think of has been tagged. So I will do my best.

1. Cory Mawhorter: Cory is a past co-worker and friend. He went on to become a professional vagabond and created FLIR (FaceLift Image Replacement) – an alternative to sIFR.
2. Tony Bibbs: I don’t know you, but you started this, and have yet to be tagged. TAG *runs*
3. Jack Bauer
4. I give up.
5. -
6. -
7. -

Ok, so, I failed. Anyways, here are the rules for… Cory & Jack to follow:

• Link your original tagger(s), and list these rules on your blog.
• Share seven facts about yourself in the post – some random, some weird.
• Tag seven people at the end of your post by leaving their names and the links to their blogs.
• Let them know they’ve been tagged by leaving a comment on their blogs and/or Twitter.