You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@esme.apache.org by "Hirsch, Richard" <ri...@siemens.com> on 2009/02/02 09:57:18 UTC
Memory leak?
Do we have a memory leak somewhere?
Take a look at the process memory at the stax site. There are no TCP
connections but process memory keeps on increasing.
D.
Re: Memory leak?
Posted by David Pollak <fe...@gmail.com>.
There may be a memory leak.
I'm seeing memory leaks on Lift 0.10 based sites. I'm hoping to track them
down very soon... but between the book and the ESME sprint that ends this
week... it won't likely happen this week. :-(
On Mon, Feb 2, 2009 at 12:57 AM, Hirsch, Richard <richard.hirsch@siemens.com
> wrote:
> Do we have a memory leak somewhere?
>
> Take a look at the process memory at the stax site. There are no TCP
> connections but process memory keeps on increasing.
>
> D.
>
>
>
>
>
--
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Git some: http://github.com/dpp
Re: Memory leak?
Posted by Bertrand Delacretaz <bd...@apache.org>.
On Mon, Feb 2, 2009 at 10:18 AM, Hirsch, Richard
<ri...@siemens.com> wrote:
> Here is the screenshot (http://esmeproject.googlecode.com/files/stax%20memory.jpg) since apache mailing lists don't allow attachments.
Some attachments are allowed on our lists, though I'm not sure about
the exact rules. http://markmail.org/message/oyifjsatt3oicspo for
example attaches at PDF document.
-Bertrand
Re: Memory leak?
Posted by Vassil Dichev <vd...@apache.org>.
Is this 100k I'm seeing? This is not yet a reason to worry- a regular
IDE consumes much more usually ;-) Maybe the application hasn't
reached a threshold level to do a full GC. Let's give it more time and
check again (the app has been running for less than a day).
> Isn't going to help us on stax where there is no file system access.
The options provided enable logging to stdout/stderr, so should work.
> Have you seen the comments on the last ESME blog (http://blog.esme.us/results-esmes-first-load-test/) and the latest stax blog (http://developer.stax.net/profiles/blogs/load-testing-on-stax) about cloud-based performance issues? I'd add your comments there.
I checked these but haven't thought much about performance yet so can't comment.
AW: Memory leak?
Posted by "Hirsch, Richard" <ri...@siemens.com>.
Isn't going to help us on stax where there is no file system access.
Have you seen the comments on the last ESME blog (http://blog.esme.us/results-esmes-first-load-test/) and the latest stax blog (http://developer.stax.net/profiles/blogs/load-testing-on-stax) about cloud-based performance issues? I'd add your comments there.
D.
-----Ursprüngliche Nachricht-----
Von: vdichev@gmail.com [mailto:vdichev@gmail.com] Im Auftrag von Vassil Dichev
Gesendet: Montag, 02. Februar 2009 10:49
An: esme-dev@incubator.apache.org
Betreff: Re: Memory leak?
Could you please set MAVEN_OPTS to the following and run it again:
-verbose:gc -XX:+PrintGCDetails -XX:+PrintClassHistogram
Re: Memory leak?
Posted by Vassil Dichev <vd...@apache.org>.
Could you please set MAVEN_OPTS to the following and run it again:
-verbose:gc -XX:+PrintGCDetails -XX:+PrintClassHistogram
AW: Memory leak?
Posted by "Hirsch, Richard" <ri...@siemens.com>.
Here is the screenshot (http://esmeproject.googlecode.com/files/stax%20memory.jpg) since apache mailing lists don't allow attachments.
D.
-----Ursprüngliche Nachricht-----
Von: Hirsch, Richard
Gesendet: Montag, 02. Februar 2009 09:57
An: esme-dev@incubator.apache.org
Betreff: Memory leak?
Do we have a memory leak somewhere?
Take a look at the process memory at the stax site. There are no TCP
connections but process memory keeps on increasing.
D.