我們完成上裝我們的XCache和eAccelerator插入的最新的版本，現在版本0.6。

為錯過的那些您 最初的公告我們寫了 二 插入 那讓WordPress直接地與用於XCache和eAccelerator促進表現和減少輸入/輸出活動的內存駐留的opcode PHP易變的貯藏所聯絡。

eAccelerator 并且 XCache 是貯藏引擎為PHP的二最普遍的打開來源opcode，并且我們高度建議中的任一和所有主人使用他們由幾摺疊改進PHP表現。 特別是，我們推薦XCache為最佳的表現。

…

我們在移動工作向一臺新的服務器所有星期，并且我們完成了轉折。 最好所有，我們中間交換了到新的服務器，不用任何停工期。 我們新的服務器是1.86千兆赫核心2二重奏和與DDR2 RAM 3GB -所有感謝對令人敬畏的人和加侖在 Lunarpages那裡最佳的主人是。

很多工作進入這轉折希望提高表現-和更加重要地，可靠性-我們的服務器。 在去年(自從我們首先開始了我們主持與LP)，我們從幾百萬命中去每月許多成千上萬，并且我們的老服務器相當採取了命中。 為此，我們集中於部署輕量級和高優化代碼所有; 有希望地那兒不會無意想不到的停工期…。

我們的當前軟件設定是非常複雜的，但有希望地它一直把我們帶對是我們的目標的0.00分鐘停工期-! 我們有多種應用軟件服務器和節目跑在背景做什麼的其中每一好他們-而不是傳統有這網服務器做它所有方式。 在，我們當前有一個軟件堆棧包括這些產品之時一個tightly-knit濾網：

…

Congratulations are in order for Microsoft’s IIS development team - today they’ve just announced the public availability of the final version of the IIS-FastCGI ISAPI Extension - a long-awaited and much-improved way of running just about any open-source scripting engine on IIS, safely and quickly.

This FastCGI module for IIS 5.1, 6, and 7 (with Windows Vista and Server 2008) have been in the works for quite a while now, and we’ve been using them since the first beta release - they’re good. While the biggest benefit will be seen in using FastCGI w/ IIS7 to take advantage of the new kernel-mode caching, it’s still a huge improvement over the old way of running scripting engines for languages like PHP on Windows.

The Problem: Most open-source scripting engines like PHP and Ruby on Rails were initially developed on/for the *nix world. On Unix-based platforms, the easiest way of creating multi-threaded applications is just to run the same app twice or more (The CGI model). On Windows, that doesn’t work out so well, because it takes a lot more resources to create another process. So these engines released Windows-specific single-process multi-threaded engines; the only problem was, they weren’t stable. Too many race conditions in some very non-thread-safe code wreaked havoc on many Windows systems, with the PHP developers themselves giving “Stability on IIS” the lowest level of concern.

…

For all the Windows-bound PHP users out there, consider yourselves warned: even if you’re running the (supposedly) thread-safe PHP Win32 binary redistribution, you’re still susceptible to PHP Access Violation Errors, race problems, heap corruption, and much worse if you use the popular eAccelerator opcode-caching extension.

We did our testing with the binaries compiled by SiteBuddy using the latest versions of both PHP and eAccelerator. Almost immediately after initiating a stress test on our test servers we experienced the dreaded “PHP Access Violation” error - which brings down the entire IIS Worker Process to its heels.

…

PHP Fatal error:  require_once()[function.require]: Failed opening
required 'SAM/php_sam.php' (include_path='.;C:php5pear') in
sam_factory on line 1

…