> thanks for the info Ronnie. Seems as though apache is buffering, as > my results are still being truncated. time to start thinking up > another idea i suppose.
I guess fconfigure [web::response] -blocking true flush [web::response] doesn't really change anything as blocking should be true by default... Q: Do all your requests use that much memory? Cause then cleaning up doesn't help anyway. Other ideas could be: Make your process use less memory (e.g. process files line by line instead of reading them completely into memory...). Or setting up different interpreter pools for low memory requests and high-memory requests: if high-memory requests are a rare thing then at least you don't "infest" all interpreters with high memory usage. That doesn't solve the problem of using lots of memory, but at least you can still use some interpreters multiple times w/o having to cleanup after every request. (Depending on the application setup, that probably doesn't help.) Or use Websh in CGI mode for the expensive requests as all the memory will be freed by the OS after every call. -> Memory consumption of the other requests (handeled by mod_websh) will be low and shorttime high-memory usage is really limited to the specific request. hth Ronnie -- Ronnie Brunner | [EMAIL PROTECTED] phone +41 (0)44 247 79 79 | fax +41 (0)44 247 70 75 Netcetera AG | 8040 Zürich | Switzerland | http://netcetera.ch --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
