Terry Ellison

@lazy404 wrote: > The basic idea is to use a file on tmpfs as a shared memory, this enables us to attach to same memory segment from processes not forked...

> currently we use MAP_FIXED ... I also did a trawl on this, and most of the *nix-based solutions are a hack. At best you can do mapping collision detection...

@lazy404, so its a case of +1 on the sharing of SMAS :-). This is all complicated and not very intuitive. It's taken me a year to get my head...

> ... code duplication impacting the vm cache in scripts which include same files from different starting points, and cases where code inclusion is based of some script parameters, in...

> ... we use open_basedir ... There's a flaw in this open_basedir code in that its terribly sub-optimal and craters NFS performance. I had an exchange with Rasmus over this...

@lazy404, an off-the-wall thought: it would be fairly easy to swap out the per-script file-based cache with, say, a memcached listening only on a socket. This could be shared across...

@lazy404, > we can put the cache on a SSD and let the OS decide what data is hot, this enables us to virtually cache all php files. > security...

Yup, the compression ratio is good. Try `opcache.compression_algo=3` the LZ4H algo takes longer to compress on the compile pass but the compression ratio is better and the explode time faster....

At the moment the MLC model assumes a single request per image activation -- that is _not_ using --enable-fastcgi, but one of the dialogues that I want to have with...

@lazy404, thanks for this, but can we move the mod_fcgid discussions to issue #6?