Hibernate Books

All times are UTC - 5 hours [ DST ]



Post new topic Reply to topic  [ 3 posts ] 
Author Message
 Post subject: consumed memory
PostPosted: Mon Dec 19, 2011 6:44 am 
Regular
Regular

Joined: Thu Jun 16, 2011 12:03 pm
Posts: 94
Hi all,

I think I am facing a problem with my memory in my JBoss hibernate Search project.

I am using 3.4.1 Hibernate Search library and JBOSSAS 6.1.0.Final. The development server has 2.5 GB of memory. The JVM has 1GB assigned.

I changed all my hbm files to lazy=true because other way the system did not work efficiently and all the memory was consumed.

After two days executing queries, the development system seems to consume almost all the memory leaving just about 200MB. I don't know if the project can consume all the memory causing trobles to the JBoss.

I would like to put my project in my production system but I do not know if this could be a problem.

Thanks in advance,

Hibernator,


Top
 Profile  
 
 Post subject: Re: consumed memory
PostPosted: Mon Dec 19, 2011 6:53 am 
Hibernate Team
Hibernate Team

Joined: Thu Apr 05, 2007 5:52 am
Posts: 1689
Location: Sweden
Hi,

this is a hard question to answer with the information you provided. How much memory was consumed directly after the start? Do you have any caches configured which are filling up? In this case you have to measure the memory consumption after a warm up period. Also, does the memory footprint increase even further maybe even leading to a OutOfMemory exception. I think you don't get around a load test, including some profiling. You want to find out which objects are consuming the memory. It might not even be Hibernate (Search) related.

Setup a load test and attach with a profiler. Once you know where the memory is consumed it will be much easier to find the exact cause of the problem.

--Hardy


Top
 Profile  
 
 Post subject: Re: consumed memory
PostPosted: Wed Dec 21, 2011 1:09 pm 
Hibernate Team
Hibernate Team

Joined: Fri Oct 05, 2007 4:47 pm
Posts: 2296
Location: Third rock from the Sun
To add to Hardy's reply, I'd not be concerned unless you can find a problem: with Java servers it's natural that they try to use most available memory to make the most out of it. You definitely want to have a look with a profiler, or memory consumption alone isn't a good metric.

Also, you could enable GC activity logging by using the Java command line parameters; an indication of your system suffering from lack of memory is frequent and long garbage collection runs, especially if they are of the "stop the world" type.

_________________
Sanne
http://in.relation.to/


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 3 posts ] 

All times are UTC - 5 hours [ DST ]


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
© Copyright 2014, Red Hat Inc. All rights reserved. JBoss and Hibernate are registered trademarks and servicemarks of Red Hat, Inc.