Summary: SE Toolkit

From: Steven Aizic <saizic_at_rogers.com>
Date: Wed Jul 10 2002 - 08:13:50 EDT
Question:
---------

I have installed the SE toolkit on an Ultra 60, trying to re-learn about
diagnosing performance bottlenecks.

1) How do you use the "aw.se" program?  I'm trying the command "se aw.se -a" ..
but it is just not working out.

2) What is the best practice on using the SE toolkit?  I'd like to gather
statistics for about 1-1.5 weeks, and then analyze them?  Is the SE toolkit
even good for this, or is there alternatives?  I seem to be able to only
view live data, but not gather data 24 hours a day?

Any help is most appreciated.  I will summarize.

Answers:
--------

The general consensus was to use Orca - http://www.orcaware.com

------------------------------------------------------------------
Matt Ryanczak ryanczakm@arin.net

You might want to check out orcallator, it's an SEToolkit script that
feeds info top a program called orca which will generate historic
performance graphs. Goto http://www.orcaware.com. It's free too...
------------------------------------------------------------------
Kevin Buterbaugh Kevin.Buterbaugh@lifeway.com

     I'm not a big fan of the SE Toolkit for two reasons:  1) I don't like
an application to modify kernel parameters without asking my permission or
even letting me know that it did so (maybe the current version doesn't do
that any more, but the last version I used sure did).  2) I don't have
time to learn yet another programming language.  I know shell, Perl, C, and
Java, but I'm not taking the time to learn SE.

     For gathering of historical data on system performance, I'd highly
recommend using sar.  Once you set it up, you're gathering data 24 x 7.
See the man page for sa1 if you're not familiar with setting up sar.

     I've written a (highly customized for our site) Perl script which
looks at the sar data file on each of our servers at the end of every day
and sends me an e-mail summary of the "problems" found (i.e. values
exceeding the thresholds I define in the script).  It's plain ascii - no
cute pie charts or multi-colored graphs, but it tells me exactly what I
need to know about my servers.

     As an aside, if you haven't already done so, I'd recommend picking up
a copy of "System Performance Tuning, 2nd Edition" by Musumeci and
Loukides (O'Reilly and Associates).  It's much more up to date at this point
than the classic "Sun Performance and Tuning, 2nd Edition" by Cockcroft and
Pettit.  HTH...
------------------------------------------------------------------
Julie Baumler julie.x.baumler@co.multnomah.or.us

Hi Steve -

I can't answer your first question, but maybe I can help with the second.
I use SE to gather performance data (a snapshot every 5 minutes all the
time) and keep the data in files.  We use system accounting on some
systems to gather the same data, but it's more work and uses up a lot of
space in the /var filesystem; so we are transitioning to SE.  I run the attached
script out of cron; the script puts the data I need in files.  You could
do a lot more in SE with the data, but we have SAS scripts that process this
data and do data trending.  As far as I know, you can't do trending with
SE, so we do all the processing with SAS (plus, this minimizes the load on the
production systems we are monitoring.)  I've attached my script and the
library I call, hopefully you will find the examples useful.
------------------------------------------------------------------
Darren Dunham <ddunham@taos.com>

You might want to take a look at the "orca" package.

It uses a script which runs a se to collect data at 5 minute intervals.
It then parses the output files and plugs the data into a RRD database,
and plots the data into files that can be viewed in a browser.

The RRD databases have a max size, and you can toss the ascii files
generated by the se script if you want.

Even if you don't want to use ORCA directly, it might be instructive
just to look at the 'orcallator' se script.
------------------------------------------------------------------
Richard Sullivan <RSullivan@espeed.com>

the tool kit has some cool features but the best way is just to collect sar
vmstat iostat etc. etc. data then write some perl to graph it.......or if u
have some cash get somethign like team quest.....
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
Received on Wed Jul 10 08:17:54 2002

This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:42:48 EST