I saw these on this page: http://www.lascon.co.uk/d005002.htm
Also, The latest performance tuning guide database performance section: http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/index.jsp?topic=/com.ibm.itsmm.doc/b_perf_tuning_guide27.htm Regards, Shawn ________________________________________________ Shawn Drew Internet [EMAIL PROTECTED] Sent by: ADSM-L@VM.MARIST.EDU 08/21/2008 04:17 AM Please respond to ADSM-L@VM.MARIST.EDU To ADSM-L cc Subject Re: [ADSM-L] DB Mirroring - Poll and question Why not use some old IBM scripts when comparing performance??? The scrips was orginally published under "How to determine when disk tuning is needed for your ITSM server" at http://www-1.ibm.com/support/docview.wss?uid=swg21141810. See discussion at http://www.mail-archive.com/adsm-l@vm.marist.edu/msg51968.html "On my first test expire run on my new test server (to which I reloaded the 194GB production DB), the expire ran in 10-hours - 1/4 of the usual time." Reload = Unload + load DB, or only a restore DB? //Henrik -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Schneider, Jim Sent: den 21 augusti 2008 00:06 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] DB Mirroring - Poll and question (using small voice) I guess it's not "lots." 124,858,663 files, 131 TB occupancy, 90 GB database, ~100 clients. Jim -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Nicholas Rodolfich Sent: Wednesday, August 20, 2008 4:33 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] DB Mirroring - Poll and question WOW, the 342 Million files is what is killing you but it still seems like an excessive amount of time. You mentioned Saturday as when it starts. You are running expiration daily aren't you? You should be able to run expiration and reclamation to completion each day or you need to look at another instance or configuration to meet your resource needs. If you don't complete expiration and reclamation daily, you will be queueing up unfinished work each day that will turn into a 24-48 hour expiration run(sounds like you are there). Expiration and reclamation go hand-in-hand. If your expiration doesn't complete then you reclamation can't either. As a result, you may have a good number of un-reclaimed and un-expired entries in your database. BTW, I have always been told, by my TSM mentors, that due to the database intensive nature of expiration, that it should always run by itself. Define LOTS? My specs are: 194GB DB 206TB Occupancy 342,194,690 files "Schneider, Jim" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> 08/20/2008 01:58 PM Please respond to "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> To ADSM-L@VM.MARIST.EDU cc Subject Re: [ADSM-L] DB Mirroring - Poll and question We need 4-6 hours for 90GB DB, ~100 clients. The servers have LOTS of files. -----Original Message----- From: ADSM: Dist Stor Manager Michael Green Sent: Wednesday, August 20, 2008 12:48 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] DB Mirroring - Poll and question 48 hours sounds like an awfully looong time to me. On my busiest Linux server (90gb DB, ~100 clients) expiration completes in 20-30 minutes. -----Original Message----- From: Zoltan Forray/AC/VCU <[EMAIL PROTECTED]> Sent: Wednesday, August 20, 2008 18:14 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] DB Mirroring - Poll and question On my big, 194GB production Linux server, an EXPIRE INVENTORY runs 40-48 hours. Granted, the server is very busy performing other tasks such as client backups, stgbackups and such. The DB buffers and such are configured identically to the production server. On my first test expire run on my new test server (to which I reloaded the 194GB production DB), the expire ran in 10-hours - 1/4 of the usual time. ------------------------------------------------------------------- The information contained in this message may be CONFIDENTIAL and is intended for the addressee only. Any unauthorised use, dissemination of the information or copying of this message is prohibited. If you are not the addressee, please notify the sender immediately by return e-mail and delete this message. Thank you. This message and any attachments (the "message") is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. Please note that certain functions and services for BNP Paribas may be performed by BNP Paribas RCC, Inc.