Re: Expiration after TSM upgrade from 5.1.6.4 to 5.2.2.1

Hi Richard!
Thank you very much for this link!
According to this article I do have a disk performance problem. One should
be able to expire more than a 1000 objects per second...
Indeed, during expiration disk utilization is way over 20% during
expiration, so I guess I should spread my database across more disks.
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines


-----Original Message-----
From: Richard Sims [mailto:rbs AT BU DOT EDU]
Sent: Friday, March 26, 2004 15:55
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Expiration after TSM upgrade from 5.1.6.4 to 5.2.2.1


>Just because I'm currently trying to boost expiration processing: I see
your
>database is rather large, how long did it take you to expire those 23194393
>objects?
>I really tried almost everything, from moving to 15k speed disks, multiple
>database volumes, moving to RAW's, the best I have seen in my environment
is
>60 objects per second.
...

In the context of this discussion, the following doc makes some interesting
observations on disk performance and expectations:

  http://www.ibm.com/support/docview.wss?uid=swg21141810

      Richard Sims    http://people.bu.edu/rbs


**********************************************************************
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.
**********************************************************************