[Swift-devel] Re: Persistent coaster service fails after several runs

Mihael Hategan hategan at mcs.anl.gov
Tue Nov 30 16:51:12 CST 2010


Can you make a heap dump of the relevant issue?

On Tue, 2010-11-30 at 09:59 -0600, Justin M Wozniak wrote:
> Along these lines, I'm looking at memory usage in Coasters.  There's a 
> plot attached below- usage spikes when the workers start running.
> 
> 96% of the usage is byte[] which makes me think it could be KarajanChannel 
> stuff...
> 
> http://www.ci.uchicago.edu/wiki/bin/view/SWFT/PerformanceNotes#Memory
> 
> On Sun, 28 Nov 2010, Michael Wilde wrote:
> 
> > This fix looks great so far - Ive tested with varying workflow sizes and delays, and have not seen any problems.
> >
> > - Mike
> 





More information about the Swift-devel mailing list