You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Schulte Marcus <ma...@bmw.ch> on 2006/02/01 07:50:57 UTC
RE: Recommended Memory Req's
It depends on how many collection-links there are between entities in your
db-model.
Try to enable hibernate-SQL logging. If you see a lot of eager loading here,
you'll be using a lot of mem (and a lot of cpu/network latency).
None of my Apps would run at a near-decent performance *without* lazy
loading. If you're getting LazyInitialisationException, try either the
session per conversation pattern, or reload all your entities from Ids using
a datasqueezer and a custom PropPersistenceStrategy.
> -----Original Message-----
> From: Chris Chiappone [mailto:chiappone@gmail.com]
> Sent: Tuesday, January 31, 2006 5:12 PM
> To: Tapestry users
> Subject: Re: Recommended Memory Req's
>
>
> I am actually not using lazy connections. When I started this project
> I was getting a lot of lazyinitializaition expections at the time. Do
> you think this could be my whats taking up a lot of memory?
>
> On 1/31/06, Schulte Marcus <ma...@bmw.ch> wrote:
> > Seems a lot of Mem to me. We're running a Tomcat with
> several small to
> > medium apps (1 Tap4, 1 Tap3, several legacy jsp) with some
> 100 concurrent
> > users. And 256 MB of Heap is way enough. So, maybe it's
> Jboss - or your app.
> >
> > What's your hibernate cache-settings. Do you use lazy
> collections? Sorry for
> > asking - but when we started to use hibernate some guys
> were upset when
> > discovering that hibernate slurped in their whole DB for
> each request ;),
> > because they didn't use lazy collections...
> >
> > > -----Original Message-----
> > > From: Chris Chiappone [mailto:chiappone@gmail.com]
> > > Sent: Tuesday, January 31, 2006 4:36 PM
> > > To: Tapestry List
> > > Subject: Recommended Memory Req's
> > >
> > >
> > > I'm just curious what the recommended amount of memory should be
> > > allocated to a medium sized appilcation running Tapestry
> 4 / Hibernate
> > > in JBOSS 4.X? Currently on my Dev box I have JBoss heap
> size set at
> > > 512. When testing my application I notice that I am pretty much
> > > maxing that out and am worried about performance on a production
> > > system with mulitple users.
> > >
> > > Thanks.
> > >
> > > --
> > > ~chris
> > >
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail:
> tapestry-user-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail:
> tapestry-user-help@jakarta.apache.org
> > >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail:
> tapestry-user-help@jakarta.apache.org
> >
> >
>
>
> --
> ~chris
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Recommended Memory Req's
Posted by Chris Chiappone <ch...@gmail.com>.
Yeah, I'm thinking of taking a look at this kickstart project. Maybe
I can adapt it to my application. If it wasn't for deadlines I would
have done something about this a long time ago. Just figure making
the change to lazy loading will take a lot of time and debugging to
make sure everything still works properly.
On 2/1/06, Schulte Marcus <ma...@bmw.ch> wrote:
> It depends on how many collection-links there are between entities in your
> db-model.
> Try to enable hibernate-SQL logging. If you see a lot of eager loading here,
> you'll be using a lot of mem (and a lot of cpu/network latency).
>
> None of my Apps would run at a near-decent performance *without* lazy
> loading. If you're getting LazyInitialisationException, try either the
> session per conversation pattern, or reload all your entities from Ids using
> a datasqueezer and a custom PropPersistenceStrategy.
>
> > -----Original Message-----
> > From: Chris Chiappone [mailto:chiappone@gmail.com]
> > Sent: Tuesday, January 31, 2006 5:12 PM
> > To: Tapestry users
> > Subject: Re: Recommended Memory Req's
> >
> >
> > I am actually not using lazy connections. When I started this project
> > I was getting a lot of lazyinitializaition expections at the time. Do
> > you think this could be my whats taking up a lot of memory?
> >
> > On 1/31/06, Schulte Marcus <ma...@bmw.ch> wrote:
> > > Seems a lot of Mem to me. We're running a Tomcat with
> > several small to
> > > medium apps (1 Tap4, 1 Tap3, several legacy jsp) with some
> > 100 concurrent
> > > users. And 256 MB of Heap is way enough. So, maybe it's
> > Jboss - or your app.
> > >
> > > What's your hibernate cache-settings. Do you use lazy
> > collections? Sorry for
> > > asking - but when we started to use hibernate some guys
> > were upset when
> > > discovering that hibernate slurped in their whole DB for
> > each request ;),
> > > because they didn't use lazy collections...
> > >
> > > > -----Original Message-----
> > > > From: Chris Chiappone [mailto:chiappone@gmail.com]
> > > > Sent: Tuesday, January 31, 2006 4:36 PM
> > > > To: Tapestry List
> > > > Subject: Recommended Memory Req's
> > > >
> > > >
> > > > I'm just curious what the recommended amount of memory should be
> > > > allocated to a medium sized appilcation running Tapestry
> > 4 / Hibernate
> > > > in JBOSS 4.X? Currently on my Dev box I have JBoss heap
> > size set at
> > > > 512. When testing my application I notice that I am pretty much
> > > > maxing that out and am worried about performance on a production
> > > > system with mulitple users.
> > > >
> > > > Thanks.
> > > >
> > > > --
> > > > ~chris
> > > >
> > > >
> > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail:
> > tapestry-user-unsubscribe@jakarta.apache.org
> > > > For additional commands, e-mail:
> > tapestry-user-help@jakarta.apache.org
> > > >
> > >
> > >
> > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail:
> > tapestry-user-help@jakarta.apache.org
> > >
> > >
> >
> >
> > --
> > ~chris
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
--
~chris
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org