Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "David Chatterton" <chatz@omen.melbourne.sgi.com>
To: Larry McVoy <lm@neteng.engr.sgi.com>,
	linux@yon.engr.sgi.com, miguel@nuclecu.unam.mx,
	shaver@neon.ingenia.ca
Cc: ptg@melbourne.sgi.com
Subject: Re: nifty tools on Linux/IRIX
Date: Thu, 29 May 1997 09:01:47 -0500	[thread overview]
Message-ID: <9705290901.ZM19528@omen.melbourne.sgi.com> (raw)
In-Reply-To: Larry McVoy <lm@neteng.engr.sgi.com> "nifty tools on Linux/IRIX" (May 28, 12:24pm)

On May 28, 12:24pm, Larry McVoy wrote:
| Subject: nifty tools on Linux/IRIX
| Miguel asked about cool tools.  Talk to Ken, he's the man.
|

Miguel,

Hi! I work for Ken on the Performance Co-Pilot. Our only external pages are:

	http://www.sgi.com/Products/hardware/challenge/CoPilot/CoPilot.html
	http://reality.sgi.com/chatz

The first is the marketing page to the real world, the second is my home page
which has some snapshots. Our next release will include support for little
endian machines, so we have been testing this under linux (of course :).

Here is a quick summary of how it all works. We have a daemon on each host you
want to monitor. Attached to this daemon (dlopen, pipe, socket etc.) are agents
that collect performance metrics from a particular domain (kernel, web server,
database). Our client tools connect to the daemon (socket) and request metrics.
The daemon requests the metrics from the appropriate agent and forwards the
values back to the clients. One client is a logger which generates archives
that all the other clients can replay, as if they were connected live to a
daemon process. The whole protocol is very light weight, much lighter than
SNMP, so the daemon and agents rarely show up in top.

Performance Co-Pilot has only been released for IRIX, but bits have been built
under linux before, and as several of us have linux boxes at home, this will
probably continue. We have talked about making some linux binaries freely
available and other similar options, but nothing definate yet. I guess we need
to know that such an investment of our time is going to be worthwhile, and that
this fits in with our medium-long terms plans for the product. We also have to
consider Java, NT (*sigh*) etc., and determine how SGI can start releasing
software for other platforms.

We are all (quiet) supporters of the linux on SGI project, keep up the good
work!

David

-- 
David Chatterton                            (61-3) 9882 8211 (Tel)
R&D Software Engineer		            (61-3) 9882 8030 (Fax)
Performance Tools Group               http://reality.sgi.com/chatz
Silicon Graphics Pty.Ltd., 357 Camberwell Rd, Melbourne, Australia

      reply	other threads:[~1997-05-28 23:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-05-28 19:24 nifty tools on Linux/IRIX Larry McVoy
1997-05-29 14:01 ` David Chatterton [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9705290901.ZM19528@omen.melbourne.sgi.com \
    --to=chatz@omen.melbourne.sgi.com \
    --cc=linux@yon.engr.sgi.com \
    --cc=lm@neteng.engr.sgi.com \
    --cc=miguel@nuclecu.unam.mx \
    --cc=ptg@melbourne.sgi.com \
    --cc=shaver@neon.ingenia.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox