[Swift-devel] hprof profiling of coaster services

[Allan Espinosa]

ok this looks like a good replicable case.

the workflow is 2000 invocations of touch using 066-many.swift

run04.tar.gz (logs and a "top -b"  dump for the coaster service).  cpu
utilization averages to 99-100% .   i ran this for five trials and got
the same results.

run05.tar.gz - same run with profiling information. in java.hprof.bin

2009/6/19 Mihael Hategan <hategan at mcs.anl.gov>:
> On Fri, 2009-06-19 at 18:30 -0500, Allan Espinosa wrote:
>> here's a script recording without profiling of top:
>>
>> http://www.ci.uchicago.edu/~aespinosa/top_vanilla.gz
>>
>> it still consumes some cpu. but does not spike to 200% utilization.
>
> Right, 10% != 200%.
>
> Now, as you're probably already guessing, I would need:
> 1. a situation (workflow/site/etc.) in which the usage does go crazy
> without the profiler (as in what triggered you getting kicked off
> ranger); repeatable
> 2. a profiler dump of a run in such a situation
>
> Btw, the ranger issue, where was swift running?

on communicado.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: run04.tar.gz
Type: application/x-gzip
Size: 2130511 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/swift-devel/attachments/20090623/f9e9d16e/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: run05.tar.gz
Type: application/x-gzip
Size: 2306688 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/swift-devel/attachments/20090623/f9e9d16e/attachment-0001.bin>