The thing with the ArtifactInfo stuff is that you're not lazy-loading any more, you're getting every service implementation, screen, form, menu, etc all in memory at the same time. Currently in OFBiz that's a lot of stuff and it takes up a fair bit of memory. It could possibly be optimized to use less memory for the same stuff, but one way or another it's a lot of stuff.
-David On Feb 8, 2010, at 6:07 PM, Adrian Crum wrote: > Thanks Ean, that's what I meant to say but couldn't find the words. I wasn't > finding fault with the artifact info screen, instead I was trying to say it > is revealing a memory problem, so we should definitely keep it. > > -Adrian > > --- On Mon, 2/8/10, Ean Schuessler <e...@brainfood.com> wrote: > >> From: Ean Schuessler <e...@brainfood.com> >> Subject: Re: Demo Servers Down? >> To: dev@ofbiz.apache.org >> Date: Monday, February 8, 2010, 2:44 PM >> David E Jones wrote: >>> It's a nice thing to have, but maybe we should disable >> the ArtifactInfo screen on the demo server. I guess either >> that or we need more memory for the demo. >>> >> That will probably just mask the memory problem. It will >> still go down >> when people work their way through enough of the screens. >> What may be >> more critical is to ensure that memory is being released >> (dereferenced) >> more aggressively when memory gets tight. >> >> -- >> Ean Schuessler, CTO >> e...@brainfood.com >> 214-720-0700 x 315 >> Brainfood, Inc. >> http://www.brainfood.com >> >> > > >
