> Probably, but not serializing at all, and stuffing the data directly into > shared memory would perhaps be faster, at least as I vaguely understood > the results of a thread on serialization on this very forum from a month > or two ago. (Check archives for "serialize" "shared memory" and "Rasmus > Lerdorf" who weighed in with a succinct explanation of how to avoid > serialization if that performance hit was really a problem (unlikely as > that was))
You're looking for this topic: From: Josh Whiting <[EMAIL PROTECTED]> To: php-general@lists.php.net Date: Jan 3, 2005 5:28 PM Subject: [PHP] Persistent PHP web application? and this response by Rasmus: From: Rasmus Lerdorf <[EMAIL PROTECTED]> To: Josh Whiting <[EMAIL PROTECTED]> Cc: php-general@lists.php.net Date: Jan 4, 2005 6:40 PM Subject: Re: [PHP] Persistent PHP web application? The important functions were apc_fetch(), and apc_store() IIRC. > > -- > Like Music? > http://l-i-e.com/artists.htm > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
