Re: Function caching...

* Kristian Koehntopp wrote: > Another problem is the setup time for large data structures, ACK. > The second and third problem are only cured properly by an > application server, that is, a long running, multithreaded, > single process with a UID different from the webserver which > does run only a single script, but does so across multiple web > requests to that script. It's time to have an PHP application server. I'm currently freelancing for a company that integrates shopping microsites into big search engine sites with millions of products and large category trees. Currently, they are caching many things in shared memory, but that isn't very comfortable (not a good handling if you've got a cluster of web servers, shared memory doesn't work across various servers). The developers shifted their software from mod_perl to mod_php, but they really missed mod_perl's feature to save large data structures who are available for all other PHP scripts (shared memory, as mentioned above, is no good solution). > turning them into memory hogs. A proper native implementation is > needed instead. ACK, BIG ACK. Greetings, Björn.