Re[2]: [PECL-DEV] apc

From: Date: Thu, 17 Feb 2005 09:35:32 +0000
Subject: Re[2]: [PECL-DEV] apc
References: 1 2 3 4 5  Groups: php.pecl.dev 
Request: Send a blank email to pecl-dev+get-2018@lists.php.net to get a copy of this message
Hello Rasmus, Wednesday, February 16, 2005, 11:06:40 PM, you wrote: RL> Why would you want to serialize the opcodes and copy them around? That RL> would slow APC to a crawl. The way it is done today the opcode array is RL> allocated directly out of shared memory and the executor executes them RL> directly from there. sorry, but i've just checked out apc from cvs and see that it's still copying opcodes for script body, functions and classes. first time it copies them when caching, then it copies them back each time when script is executed from cache. so, it's almost equal to serializing (copying) and deserializing (copying back). i don't see why it'd be slower why i suggest to use serialize/deserialize functions? because it would allow to share code (existing working code in bcompiler), otherwise re-writing apc_compile.c is required -- Best regards, val mailto:val@vk.kiev.ua

« previous php.pecl.dev (#2018) next »