Re: Help me convincing IBM please!!!!

One thing I was recently informed of at a training class is that after
your database goes past the 40GB mark performance really starts hurting.
I bet this is the issue. 
Anyways here are my stats. 
48GB DB 75% util
ACTIVITY                     Date                Objects Examined Up/Hr
------------------     ----------     ---------------------------------
EXPIRATION             2005-03-08                               3135600
EXPIRATION             2005-03-09                               2912400
EXPIRATION             2005-03-14                               2815200
EXPIRATION             2005-03-15                                752400
EXPIRATION             2005-03-22                               3985200
EXPIRATION             2005-03-24                               1620000
EXPIRATION             2005-03-25                                864000
EXPIRATION             2005-03-27                               3474000
EXPIRATION             2005-03-27                               3261600
EXPIRATION             2005-03-28                               4611600
EXPIRATION             2005-03-29                               7286400
EXPIRATION             2005-03-29                               1908000
EXPIRATION             2005-03-29                                216000
EXPIRATION             2005-03-30                               1882800
EXPIRATION             2005-04-01                               3740400
EXPIRATION             2005-04-04                               3636000
EXPIRATION             2005-04-04                               2347200
 

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Troy Frank
Sent: Thursday, April 07, 2005 9:57 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Help me convincing IBM please!!!!

Well now I'm a bit nervous.  My scores seem to be as bad or worse than
Eric's.  Is performance in this task basically a disk i/o, and cpu bound
task, or can other things factor in?  Just a little confused since our
server isn't THAT slow (P4-2.8ghz).  DB is sitting on mirrored 10K scsi
disks.
 
ACTIVITY                     Date                Objects Examined Up/Hr
------------------     ----------     ---------------------------------
EXPIRATION             2005-03-08                                 97200
EXPIRATION             2005-03-08                                104400
EXPIRATION             2005-03-09                                104400
EXPIRATION             2005-03-10                                100800
EXPIRATION             2005-03-11                                108000
EXPIRATION             2005-03-12                                100800
EXPIRATION             2005-03-13                                 93600
EXPIRATION             2005-03-14                                104400
EXPIRATION             2005-03-15                                 86400
EXPIRATION             2005-03-16                                104400
EXPIRATION             2005-03-17                                104400
EXPIRATION             2005-03-18                                108000
EXPIRATION             2005-03-19                                100800
EXPIRATION             2005-03-20                                 97200
EXPIRATION             2005-03-21                                 97200
EXPIRATION             2005-03-22                                421200
EXPIRATION             2005-03-23                                111600
EXPIRATION             2005-03-24                                108000
EXPIRATION             2005-03-25                                108000
EXPIRATION             2005-03-26                                 97200
EXPIRATION             2005-03-27                                104400
EXPIRATION             2005-03-28                                100800
EXPIRATION             2005-03-29                                100800
EXPIRATION             2005-03-30                                122400
EXPIRATION             2005-03-31                                104400
EXPIRATION             2005-04-01                                104400
EXPIRATION             2005-04-02                                 97200
EXPIRATION             2005-04-03                                100800
EXPIRATION             2005-04-04                                 97200
EXPIRATION             2005-04-05                                403200
EXPIRATION             2005-04-06                                108000
EXPIRATION             2005-04-07                                 75600
 
ANR1462I RUN: Command script TEST-EXP completed successfully.
 

PCT_UTILIZED     AVAIL_SPACE_MB
------------     --------------
        61.8              20000
 
 
 
Troy Frank
Network Services
University of Wisconsin Medical Foundation
608.829.5384

>>> Eric-van.Loon AT KLM DOT COM 4/7/2005 4:57:19 AM >>>
Hi *SM-ers!
Please help me with this and take the time to read this request!!!!

We're having serious performance problems with our TSM database. Part of
the discussion with IBM is how expiration should perform.
A technical document on the TSM website stated that one should be able
to expire 3.8 million objects per hour. As soon as I referred to this
document ("How to determine when disk tuning is needed") IBM removed it
from their site!!!!
Expiration runs at a speed of 140.000 objects per hour in my shop an I
know for sure that some of you are running at 3.8 million or more and I
like to prove this to IBM.

I'm begging for your help with this. I would like to ask you to issue
the following SQL statements on your TSM server(s) and send the output
directly to me: 

select activity, cast ((end_time) as date) as "Date" ,(examined/cast
((end_time-start_time) seconds as decimal(18,13)) *3600) "Objects
Examined Up/Hr" from summary where activity='EXPIRATION' and days
(end_time) -days(start_time)=0

select pct_utilized, avail_space_mb from db

The first statement calculates your expiration performance
(objects/hour) and the second one lists your database size and
utilization.
Thank you VERY much for sending me your statistics in advance, I REALLY
appreciate it!!!
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines


**********************************************************************
For information, services and offers, please visit our web site:
http://www.klm.com . This e-mail and any attachment may contain
confidential and privileged material intended for the addressee only. If
you are not the addressee, you are notified that no part of the e-mail
or any attachment may be disclosed, copied or distributed, and that any
other action related to this e-mail or attachment is strictly
prohibited, and may be unlawful. If you have received this e-mail by
error, please notify the sender immediately by return e-mail, and delete
this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its
subsidiaries and/or its employees shall not be liable for the incorrect
or incomplete transmission of this e-mail or any attachments, nor
responsible for any delay in receipt.
**********************************************************************



Confidentiality Notice follows:

The information in this message (and the documents attached to it, if
any) is confidential and may be legally privileged. It is intended
solely for the addressee. Access to this message by anyone else is
unauthorized. If you are not the intended recipient, any disclosure,
copying, distribution or any action taken, or omitted to be taken in
reliance on it is prohibited and may be unlawful. If you have received
this message in error, please delete all electronic copies of this
message (and the documents attached to it, if any), destroy any hard
copies you may have created and notify me immediately by replying to
this email. Thank you.
********************************************
This message is intended only for the use of the Addressee and
may contain information that is PRIVILEGED and CONFIDENTIAL.

If you are not the intended recipient, you are hereby notified
that any dissemination of this communication is strictly prohibited.

If you have received this communication in error, please erase
all copies of the message and its attachments and notify us
immediately.

Thank you.
********************************************