TSM Storage agent performance

Tags

agent, performance, solaris, storage

Operating Systems Solaris TSM Storage agent performance

04-15-2008

Registered User

1, 0

Join Date: Apr 2008

Last Activity: 21 August 2008, 9:24 PM EDT

Posts: 1

Thanks Given: 0

Thanked 0 Times in 0 Posts

TSM Storage agent performance

Guys,

I have TSM Lanfree on a 5220, Being an AIX Admin I'm looking for help on Solaris.

Detailed Monitoring provided by Teamquest.

The problem is that although the 'root' owned 'dsmsta quiet' process is apparently using 27 software threads they never add up to more than 1/64th of the available CPU capability (apparently 1 hardware thread). Clearly limited like that the Sytorage agent is not going to be an effective datamover process. I cannot find anything in TSM to influence this. So is there something I need to get set or changed in the OS settings to free me of this limitation.

THanks guys.

You can reach me at the_sunburned_guy@a_nice_beach_in_Hawaii.surfin {I wish}

SteveC.

SHCART

View Public Profile for SHCART

Find all posts by SHCART

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. AIX

Performance metrics between Dual Storage IOA versus other drive configurations

Greetings! We ordered a bunch of P7s as part of a hardware upgrade and I was made aware of the Dual Storage IOA configuration. This is something we hadn't fully considered and I was wondering if anyone had done any performance tests using this setup. All our IBM rep told us was "it's slower" and...

LEARN ABOUT CENTOS

pmdavmware

PMDAVMWARE(1)						       Performance Co-Pilot						     PMDAVMWARE(1)

NAME

       pmdavmware - VMware performance metrics domain agent (PMDA)

DESCRIPTION

       pmdavmware is a Performance Metrics Domain Agent (PMDA) which exports metric values from a (possibly remote) VMware virtualisation host.

       This implementation uses the VMare Perl API (refer to the online docs at http://www.vmware.com/support/developer/viperltoolkit).  VIPerl is
       a prerequisite for this PMDA, it needs to be installed and configured before attempting to use this agent.  It is highly recommended that
       you test your VIPerl installation using the demo programs that are shipped with VIPerl, before attempting to use this PMDA.

INSTALLATION

       In order to access performance data using the VIPerl API, it is necessary to be able to login to the metrics source.  Hence, a valid VMware
       server name, user name and pass word are needed by the PMDA.  These can be passed in on the command line (via the pmcd.conf file) or via a
       vmware.conf file in the PMDA directory.

	       # cd $PCP_PMDAS_DIR/vmware
	       # [ edit vmware.conf ]

       This file should contain three lines, such as:

	       $server = 'vm.server.net';
	       $username = 'XXXX';
	       $password  = 'YYYY';

       Once this is setup, you can access the names and values for the vmware performance metrics by doing the following as root:

	       # cd $PCP_PMDAS_DIR/vmware
	       # ./Install

       If you want to undo the installation, do the following as root:

	       # cd $PCP_PMDAS_DIR/vmware
	       # ./Remove

       pmdavmware is launched by pmcd(1) and should never be executed directly.  The Install and Remove scripts notify pmcd(1) when the agent is
       installed or removed.

FILES

       $PCP_PMDAS_DIR/vmware/vmware.conf
	   configuration file for the pmdavmware agent

       $PCP_PMDAS_DIR/vmware/Install
	   installation script for the pmdavmware agent

       $PCP_PMDAS_DIR/vmware/Remove
	   undo installation script for the pmdavmware agent

       $PCP_LOG_DIR/pmcd/vmware.log
	   default log file for error messages from pmdavmware

SEE ALSO

       pmcd(1).

3.8.10							       Performance Co-Pilot						     PMDAVMWARE(1)

Solaris