Eddie can you explain the differences between APC (which is now built into PHP) and EAccelerator. You seem to give mixed signals here as you endorse both it seems, but I would think they would collide and as the Highlander says, "There can be only one!" http://us.php.net/apc http://eaccelerator.net/ Why would we choose one over the other, or do they really work in tandem together? We looked into memcached or memcache or some $hit (it's too confusing and I don't remember the exact one) but after installing, we realized it would not work so well for us as it makes your SQL queries potentially stale. In our case, they all have to be live and accurate. And there is a 1MB data limit per cache object. :( http://us.php.net/manual/en/book.memcache.php http://us.php.net/manual/en/book.memcached.php http://www.danga.com/memcached/ However we did install the APC and that seems to work very well for caching the page's opcodes, and are quite pleased with it so far. Plus it's nice that it's an "official" module for PHP and a simple apt-get install. > -----Original Message----- > From: Eddie Drapkin [mailto:oorza2k5@xxxxxxxxx] > Sent: Tuesday, May 26, 2009 8:20 PM > > 2) It's easier to start with a persistent caching > setup and go from there than apply one later. Look into memcache, > memcachedb, and __apc__ for some absolutely required tools. > > 6) Install an opcode cache, I recommend __EAccelerator__. Script > CPU time will be decreased by (a) order of magnitude(s). -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
