Eclipse Community Forums: Test and Performance Tools Platform (TPTP) » Process Memory size grows fast even when profiler is in the pause mode

Home » Archived » Test and Performance Tools Platform (TPTP) » Process Memory size grows fast even when profiler is in the pause mode

Show: Today's Messages :: Show Polls :: Message Navigator

Process Memory size grows fast even when profiler is in the pause mode [message #108083]

Wed, 08 August 2007 23:15

roman

Messages: 7
Registered: July 2009

Junior Member

Hello all,
I am trying to get an execution flow information for our application. First
I was trying to run it in the "enabled" control mode like so:
-agentlib:JPIBootLoader=JPIAgent:server=enabled;CGProf:execd etails=true

But this does not seem to work and one of the bugs states that it is not
possible to get an execution flow information with JVMTI profiler in
"enabled" mode since profiler does not know complete context by the time it
connects to the application.
So I was trying to run the application in "controlled" mode and pause the
collecting of the profiling data until i am ready to execute a use case. But
what I am seeing is that memory that is occupied by my application process
grows very rapidly and quickly reaches 1.5GB or so and then I am getting out
of memory exception. My application's heap size is maxed at 512 so i am
possitive that it is a native part of the profiler that occupies all the
memory.
I am wondering what kind of information is it storing that it takes up so
much space considering profiling is on pause. Is all this "context"
information taking up so much space? Can someone explain?

Thanks,
Roman

Report message to a moderator

Re: Process Memory size grows fast even when profiler is in the pause mode [message #108636 is a reply to message #108083]

Sun, 12 August 2007 13:47

Asaf Yaffe

Messages: 333
Registered: July 2009

Senior Member

Roman Kurin wrote:
> Hello all,
> I am trying to get an execution flow information for our application. First
> I was trying to run it in the "enabled" control mode like so:
> -agentlib:JPIBootLoader=JPIAgent:server=enabled;CGProf:execd etails=true
>
> But this does not seem to work and one of the bugs states that it is not
> possible to get an execution flow information with JVMTI profiler in
> "enabled" mode since profiler does not know complete context by the time it
> connects to the application.

You are correct. Currently, "enabled" mode is not supported when
collecting full execution details.

> So I was trying to run the application in "controlled" mode and pause the
> collecting of the profiling data until i am ready to execute a use case. But
> what I am seeing is that memory that is occupied by my application process
> grows very rapidly and quickly reaches 1.5GB or so and then I am getting out
> of memory exception. My application's heap size is maxed at 512 so i am
> possitive that it is a native part of the profiler that occupies all the
> memory.
> I am wondering what kind of information is it storing that it takes up so
> much space considering profiling is on pause. Is all this "context"
> information taking up so much space? Can someone explain?
>
> Thanks,
> Roman
>
>

When data collection is paused, the profiler keeps track of each
thread's stack to maintain execution context. In theory, this should not
have a large impact on memory, unless there is a bug somewhere.

What version of Eclipse/TPTP/Java are you using? On which O/S?

--
Asaf Yaffe
Eclipse TPTP Committer, JVMTI Profiler

Report message to a moderator

Re: Process Memory size grows fast even when profiler is in the pause mode [message #108664 is a reply to message #108636]

Sun, 12 August 2007 19:11

roman

Messages: 7
Registered: July 2009

Junior Member

Asaf, thanks for your reply, I am using Eclipse 3.3 with TPTP 4.4.0.1. JDK
1.5_12. I am using external Agent Controller 4.4.0.1. The application that
i am profiling is very big, it is starting around 30 different thread at
the startup and a method stack could be deep on the order of 40 methods.
So I guess there is a lot of context information to keep track off, but
1GB of this data might be a little exessive unless I am missing something.
I am not using any class filters beyond the default one, but I didnt think
it would matter since profiling is on pause. Any ideas?

Thanks,
Roman

Report message to a moderator