Does Bricolage have a memory leak?
No. Bricolage can use a lot of memory resources, especially if you publish a lot of documents at once, such as via the SOAP interface. Perl grabs the memory it needs, but it never releases it back to the operating system, although it will reuse it before asking the OS for more. So if you’ve published a lot of stories at once or done anything else to cause Bricolage to load a lot of data (such as used the search interface to get a list of all 10,000 stories in your Bricolage database), then the process that handled your request will become quite large and stay that way for its lifetime. There are a number of ways to address this issue: • If you’re using bric_soap to execute big SOAP requests, use its –chunks option whenever possible to cut down on the amount of work any one request is doing. • Change your Apache configuration to get a better handle on your process sizes. Set MaxSpareServers and MinSpareServers to a reasonable numbers, and set MaxRequestsPerChild to limit the number of
