It is a custom webserver and we have built no caching as all pages served are dynamic. Pretty much convinced though that the problem is in the pages fetched from the child processes rather than the push to the browser as closing the child processes releases the memory.
Chris -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
