Product

• Brisque^® 5.x
• Brisque 4.1

Platform

All Brisque platforms

Operating system

IBM^® AIX^® 4.1, 5.2

Symptoms

Slow Brisque performance on all platforms.

Cause

The slow performance may be caused by IO problems.

Solution

To confirm and improve Brisque IO performance problems:

• Run the datavol-test.sh script to test the throughput of the Brisque 5.x dataVolumes (data disks). On new platforms (such as 6F1, 6E3, 6E4), the copy speed between dataVolumes should be at least 30 MB/sec. On older platforms, it should be more than 10 MB/sec.
  Check that new disks/towers (Ultra 160 and higher) are connected to adapters that are fast enough. A dual channel LVD board is recommended.
• Run the lsscsi.sh script or check the brisque_check.html log. Verify that no disk is listed as Other SCSI Disk Drive. An IBM disk should be listed as 16 Bit LVD SCSI Disk Drive, and a Seagate disk should be listed with a full description.
  If a disk is listed as Other SCSI Disk Drive, this means that its stanza (located on the diskette that was supplied with the disk) was not installed. As a result, the disk is running 4 times slower than it should. Check if the brisque_check.html log contains the following line:

svg4: hdisk4 Available 20-58-00-11,0 Other SCSI Disk Drive, 140014 MB

The above line indicates that stanza was not installed on the disk. To load the missing stanza:

1. Download add_stanza.tar.Z
2. Uncompress and untar stanza.tar.Z
3. Run the /scitex/version/scripts/add_stanza script that updates the ODM.
4. Reboot the system. The disk params are updated according to the script that you ran.

Notes:

• Running the stanza script does not affect the data on the disk.
• It was found that when a non-Creo disk was installed, the correct stanza will not be installed.
  The workaround in this case is to force a queue_depth size of “3” for each “other disk”. To increase their stanza-less write performance, run the following command for each “other disk”:
  hdev -l 'hdiskX' -a queue_depth='3' -a q_type='simple' -P
  Then reboot the system.

Technical contact(s)

Lev Weissman

Submitted by

Lev Weissman

Date submitted

22 Dec 2005