Check your default IP packet sizes and IP performance implementation.  The
more packets you have the more overhead to process them.  We do not have a
SUN TSM server, but we run SAN Storage agents and Clients on SUN.

Also, check your TDP for SAP implementation and make sure you are using the
most optimal for you environment.

I would expect you have some artificial cause of this as mentioned below.

Paul D. Seay, Jr.
Technical Specialist
Northrop Grumman Information Technology
757-688-8180


-----Original Message-----
From: Paul Ripke [mailto:stixpjr AT BIGPOND.NET DOT AU]
Sent: Tuesday, January 28, 2003 6:01 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: VERY HIGH %SYS CPU


On Wednesday, Jan 29, 2003, at 00:11 Australia/Sydney, Broderick, Sean
wrote:

> Hi,
>
> The CPU usage (%sys) is extremely high, like 80 - 90%, on the TSM
> server (Sun V880 running TSM v5.1.5) during the backup window.
> Particularly when
> TDP R3 clients are attempting their SAP backups via backint / brbackup
> and
> as such the throughput is extremely poor (<9MB/s direct to disk cache
> via
> gigabit network).

How are your disk stgpool volumes configured? Is the system paging? How much
RAM do you have? Any errors on your network interfaces? How fast does an ftp
run?

Since the vast majority of the work done by dsmserv during backups is I/O, a
high sys% CPU is to be expected. OTOH, our Sun TSM servers can hit 9 MB/s on
100 Mb ethernet, with much older hardware.

Cheers,
--
Paul Ripke
Unix/OpenVMS/DBA
101 reasons why you can't find your Sysadmin:
68: It's 9AM. He/She is not working that late.
-- Koos van den Hout