[Swift-devel] hprof profiling of coaster services

[Michael Wilde]

Yes, sorry, I meant to paste it at the bottom of the previous message 
but forgot. The sysadmin message is at the bottom of the thread below.

-------- Original Message --------
Subject: Re: Ranger @ TACC - Jobs Running On Head Node creating heavy load
Date: Wed, 17 Jun 2009 15:26:37 -0500
From: Allan Espinosa <aespinosa at cs.uchicago.edu>
To: Zhao Zhang <zhaozhang at uchicago.edu>
CC: wilde at mcs.anl.gov
References: <1245269425.13629.23.camel at lockman-d630.tacc.utexas.edu>	 
<4A394FBD.5040301 at uchicago.edu>	 
<50b07b4b0906171322k26976392s4a99144749c437e7 at mail.gmail.com>

Zhao,

your coaster services and gram call back daemons are eating 2cores.
You should kill these too as you abort your swift run.

-Allan

2009/6/17 Allan Espinosa <aespinosa at cs.uchicago.edu>:
 > I am guessing that these are the coaster services running on the GRAM
 > head node (gateway.ranger points to login3.ranger).
 >
 >
 > I made the run last night.  I am currently running stuff on teraport.
 >
 > 2009/6/17 Zhao Zhang <zhaozhang at uchicago.edu>:
 >> Hi, Mike
 >>
 >> That is me and Allan. I am running the remaining part of the AMPL 
work flow,
 >> 800 job left. What shall I do now?
 >>
 >> zhao
 >>
 >> John Lockman wrote:
 >>>
 >>> Dr. Wilde,
 >>>
 >>>
 >>> Two users on your project, [zzhang & tg802895] are running jobs on the
 >>> Ranger head node [login3] which is slowing the system down dramatically
 >>> for other users.
 >>> Can these jobs be run on the compute nodes and not the head node?
 >>>
 >>>
 >>> Thanks,
 >>>


On 6/26/09 7:52 AM, Ben Clifford wrote:
>> In other words, the Ranger sysadmin did not say "your coaster process is 
>> consuming CPU", he just said your jobs are causing the login3 host to be 
>> slow for other users.
> 
> Do you have what the Ranger sysadmin actually said, in its entirety?
>