Re: APC caching keys.
| From: | Jochem Maas | Date: | Mon, 21 Nov 2005 10:54:05 +0000 |
| Subject: | Re: APC caching keys. | ||
| References: | 1 2 3 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-226186@lists.php.net to get a copy of this message | ||
Marcus Bointon wrote:
On 19 Nov 2005, at 04:07, Curt Zirzow wrote:I guess I'll have to try a build myself a copy of APC from cvs - operative word being try :-/ having said that I don't use __autoload() - I did but it was just a PITA - but I wonder if the segfault still occurs if there are situations that occur (missing class[es]) that cause the engine to check-for/try-to-run __autoload() (even though it doesn't due to the fact that its not defined)?? thanks for the feedback!If you are using mysql i would use the SQL_CACHE flag, it will eliminate the need for you to manage the cache.You don't necessarily need to us the SQL_CACHE flag in queries - you can just turn on the query cache globally using query_cache_type=1 in your my.cnf. Otherwise I quite agree - and MySQL has the huge advantage that it will work very nicely across multi-server deployments: http://dev.mysql.com/doc/refman/5.0/en/query-cache.htmlThe last version of php5.1 i have installed APC on is a cvs snapshot of around Feb 4 2005 11:49:05. Nothing special was needed.The current 3.0.8 release of APC is broken in PHP 5.1.0-dev if you ever use __autoload. It will be fixed in 3.0.9 (and is fixed in CVS), though Rasmus implied that 3.0.9 is waiting until 5.1 release.
Marcus