Home
TeamSite
TeamSite, LiveSite and OpenDeploy
per-process memory limit
Denise Bowker
Last week I increased our cache size to 400,000 entries. That, according to the documentation, is the maximum value allowed. Even though elsewhere it says that number should be 3x the number of assets in the largest backingstore. One of our backingstores has about 200,000 assets so I figured I'd max it out.
In our iwtrace.log file these three lines are appearing every 15 seconds
[PHP][Wed Jun 13 09:00:34 2012] The TeamSite server is approaching the per-process memory limit (used = 1425220 KB, proc-mem avail = 42696 KB).
[Wed Jun 13 09:00:34 2012] Please reduce cachesize and restart server to alleviate the problem.
[Wed Jun 13 09:00:34 2012] Server will deactivate all stores if available per-process memory falls below 1467916 KB[/PHP]
Since used + avail = 'dont fall below' limit, am I okay? Should I reduce the cache size by 1, 10, 100, 1000...? As you might imagine, recycling TeamSite is not a simple task.
Find more posts tagged with
Comments
There are no comments yet