Looking at the memory (private working set) used by the java process my Tapestry 5 app is running under, I notice that when running through the same request cycle with PRODUCTION_MODE set to true, I am getting an increase of approx 4K per repeated request. Is this typical or something to be concerned about in the context of an application with >50 <100 concurrent users, or is Tapestry reasonably aggressive in reclaiming resources? If it is not typical, any pointers on areas to look for leaks, or is this a needle in a haystack?
Thanks, Jim.
