[Swift-devel] Coaster CPU-time consumption issue

[Mihael Hategan]

On Mon, 2009-07-13 at 12:28 -0500, Michael Wilde wrote:
> >>
> >> At the time we did not have a chance to gather detailed evidence, but I 
> >> was surprised by two things:
> >>
> >> - that there were two Java processes and that one was so big. (Are most 
> >> likely the active process was just a child thread of the main process?)
> > 
> > One java process is the bootstrap process (it downloads the coaster
> > jars, sets up the environment and runs the coaster service). It has
> > always been like this. Did you happen to capture the output of ps to a
> > file? That would be useful, because from what you are suggesting, it
> > appears that the bootstrap process is eating 100% CPU. That process
> > should only be sleeping after the service is started.
> 
> I *thought* I captured the output of "top -u sarahs'id -b -d" but I cant 
> locate it.
> 
> As best as I can recall it showed the larger memory-footprint process to 
> be relatively idle, and the smaller footprint process (about 275MB) to 
> be burning 100% of a CPU.

Normally, the smaller footprint process should be the bootstrap. But
that's why I would like the ps output, because it sounds odd.

>   Allan will try to get a snapshot of this shortly.
> 
> If this observation if correct, whats the best way to find out where its 
> spinning? Profiling? Debug logging? Can you get profiling data from a 
> JVM that doesnt exit?

Once I know where it is, I can look at the code and then we'll go from
there.