| PLEX86 | ||
|
Linnut screen shots 10762
Yes, but why does it need to be in the kernel? Since you seem to like marketing bullpoo, here's a blurb on the Zend engine for PHP: Linnut screen shots 10763 OK poked his little head through the XP firewall and said: You have some real funny logic... PHP Performance Management: Zend Platform is equipped with four performance Debt Management modules that can be used to track and improve the speed and responsiveness of Web applications. These components build upon the proven track record of the Zend Performance Suite, the standard in performance Debt Management for PHP Web sites. Code Acceleration. Usually requiring no configuration or application changes of any kind, Code Acceleration involves both caching and optimization techniques performed on compiled PHP code, resulting typically, in a 3 times increase in performance. Dynamic Content Caching. The concept behind Dynamic Content Caching is that many dynamically generated Web pages render in exactly the same way numerous times. Consequently, results of the first end can be kept, and served "as-is" for further requests made to the same page, without having to actually execute the application. Dynamic Content Caching pays off with typical performance improvements from 20 to 150 times. This stuff is done entirely in user space. No kernel modules. -- - Bob Hauck - A proud member of the reality-based community. Linnut screen shots 10764 It is worth nothing that we don't know the thread context switch time from your benchmark, for at least two reasons...
|
||||||||