我们完成上装我们的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

…