For comparison:
09/06/02 10:15:26 ANR2750I Starting scheduled command EXPIRE_INVENTORY (
expire inventory du=100 ).
9/06/02 10:54:57 ANR0812I Inventory file expiration process 1182 completed:
examined 3023890 objects, deleting 5749 backup objects,
18 archive objects, 0 DB backup volumes, and 0 recovery
plan files. 0 errors were encountered.
or ~ 1260 / objects per second.
Hardware: 2way 6h1, 2 SSA adapters, 24 x 18GB SSA disks
SSA disks: configured into three RAID 5 arrays across two adapters
Example: ....-l 'ssa1' 'raid_5' 'pdisk14 pdisk15 pdisk16 pdisk17 pdisk18 pdisk19
pdisk20 pdisk32' -a stripe_size='128' '-a spare=false -a spare_exact=false' -a
spare_preferred='false' -a allow_page_splits='true' -a fastwrite='on'
This gives me hdisk5, hdisk6, hdisk7
If they arrays are RAID 0, I can get about an extra 10% out of them.
Then:
mkvg -f -y TSMSTGvg64 -s'64' -B -t 2 hdisk5 hdisk6 hdisk7
TSM DB:
unxr:/dev>lslv TSMdb
LOGICAL VOLUME: TSMdb VOLUME GROUP: TSMSTGvg64
LV IDENTIFIER: 000d9f7f10b6abf1.4 PERMISSION: read/write
VG STATE: active/complete LV STATE: opened/syncd
TYPE: jfs WRITE VERIFY: off
MAX LPs: 512 PP SIZE: 64 megabyte(s)
COPIES: 1 SCHED POLICY: striped
LPs: 258 PPs: 258
STALE PPs: 0 BB POLICY: relocatable
INTER-POLICY: maximum RELOCATABLE: no
INTRA-POLICY: center UPPER BOUND: 3
MOUNT POINT: N/A LABEL: None
MIRROR WRITE CONSISTENCY: on
EACH LP COPY ON A SEPARATE PV ?: yes
STRIPE WIDTH: 3
STRIPE SIZE: 4k
TSM LOG:
unxr:/dev>lslv TSMlogA
LOGICAL VOLUME: TSMlogA VOLUME GROUP: TSMSTGvg64
LV IDENTIFIER: 000d9f7f10b6abf1.3 PERMISSION: read/write
VG STATE: active/complete LV STATE: opened/syncd
TYPE: jfs WRITE VERIFY: off
MAX LPs: 512 PP SIZE: 64 megabyte(s)
COPIES: 1 SCHED POLICY: striped
LPs: 24 PPs: 24
STALE PPs: 0 BB POLICY: relocatable
INTER-POLICY: maximum RELOCATABLE: no
INTRA-POLICY: inner edge UPPER BOUND: 3
MOUNT POINT: N/A LABEL: None
MIRROR WRITE CONSISTENCY: on
EACH LP COPY ON A SEPARATE PV ?: yes
STRIPE WIDTH: 3
STRIPE SIZE: 4k
Notice the stripe width and stripe size.
This creates a "PLAID" array, if you like. The name is not important it is called many
things, but I use hardware striping and software striping.
More info:
---------------------------------------------------------------------------
hdisk5:
LV NAME LPs PPs DISTRIBUTION MOUNT POINT
dbdumps_lv 1600 1600 380..380..314..380..146 /home/dbdumps
dbdumps_log 1 1 00..00..01..00..00 N/A
TSMdb 86 86 00..00..65..00..21 N/A
TSMlogA 8 8 00..00..00..00..08 N/A
PHYSICAL VOLUME: hdisk5 VOLUME GROUP: TSMSTGvg64
PV IDENTIFIER: 000d9f7f10b69f2d VG IDENTIFIER 000d9f7f10b6abf1
PV STATE: active
STALE PARTITIONS: 0 ALLOCATABLE: yes
PP SIZE: 64 megabyte(s) LOGICAL VOLUMES: 4
TOTAL PPs: 1900 (121600 megabytes) VG DESCRIPTORS: 1
FREE PPs: 205 (13120 megabytes)
USED PPs: 1695 (108480 megabytes)
FREE DISTRIBUTION: 00..00..00..00..205
USED DISTRIBUTION: 380..380..380..380..175
---------------------------------------------------------------------------
hdisk6:
LV NAME LPs PPs DISTRIBUTION MOUNT POINT
dbdumps_lv 1600 1600 380..380..314..380..146 /home/dbdumps
dbdumps_log 1 1 00..00..01..00..00 N/A
TSMdb 86 86 00..00..65..00..21 N/A
TSMlogA 8 8 00..00..00..00..08 N/A
PHYSICAL VOLUME: hdisk6 VOLUME GROUP: TSMSTGvg64
PV IDENTIFIER: 000d9f7f10b6c331 VG IDENTIFIER 000d9f7f10b6abf1
PV STATE: active
STALE PARTITIONS: 0 ALLOCATABLE: yes
PP SIZE: 64 megabyte(s) LOGICAL VOLUMES: 4
TOTAL PPs: 1900 (121600 megabytes) VG DESCRIPTORS: 1
FREE PPs: 205 (13120 megabytes)
USED PPs: 1695 (108480 megabytes)
FREE DISTRIBUTION: 00..00..00..00..205
USED DISTRIBUTION: 380..380..380..380..175
---------------------------------------------------------------------------
hdisk7:
LV NAME LPs PPs DISTRIBUTION MOUNT POINT
dbdumps_lv 1600 1600 380..380..314..380..146 /home/dbdumps
dbdumps_log 1 1 00..00..01..00..00 N/A
TSMdb 86 86 00..00..65..00..21 N/A
TSMlogA 8 8 00..00..00..00..08 N/A
PHYSICAL VOLUME: hdisk7 VOLUME GROUP: TSMSTGvg64
PV IDENTIFIER: 000d9f7f10b6d0bc VG IDENTIFIER 000d9f7f10b6abf1
PV STATE: active
STALE PARTITIONS: 0 ALLOCATABLE: yes
PP SIZE: 64 megabyte(s) LOGICAL VOLUMES: 4
TOTAL PPs: 1900 (121600 megabytes) VG DESCRIPTORS: 1
FREE PPs: 205 (13120 megabytes)
USED PPs: 1695 (108480 megabytes)
FREE DISTRIBUTION: 00..00..00..00..205
USED DISTRIBUTION: 380..380..380..380..175
---------------------------------------------------------------------------
Miles
----------------------------------------------------------------------------------------------
Miles Purdy
System Manager
Agriculture and Agri-Food Canada,
Information Systems Team,
Farm Income Programs Directorate
Winnipeg, MB, CA
[EMAIL PROTECTED]
ph: (204) 984-1602 fax: (204) 983-7557
"If you hold a UNIX shell up to your ear, can you hear the C?"
-------------------------------------------------------------------------------------------------
>>> [EMAIL PROTECTED] 10-Sep-02 3:48:50 AM >>>
Hi *SM-ers!
Last week I read about Rodney Clark doing a 400 objects a second expiration.
I checked my expiration process: it's inspecting about 20 objects a second.
Ok, maybe he has got faster hardware, but 20 times faster?
I have TSM 4.2.2.0 running on a H70 with the database on raw logical volumes
(36 Gb. 10K rpm SSA disks, TSM mirroring). My database cache hit is 98.53%.
I was hoping that some people out there (with somewhat similar setup) could
share their expiration performance with me.
Does anybody have some tips? Where should I start troubleshooting?
Thank you very much in advance for your reply!
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.
**********************************************************************
