Oracle/HP Best Practices Guide for HP IO Accelerators

Single-instance performance architectures 16
Single-instance performance architectures
Hosting all data areas on the IO Accelerator
This configuration is likely to be the highest performing of all proposed solutions. It is also likely to be the
simplest to deploy, depending on your data protection needs. To create this configuration:
1. Place a filesystem on the IO Accelerator, or add the IO Accelerator devices to ASM in a
configuration that includes the appropriate level of protection for your data.
For example, you could use RAID1 or RAID10 or ASM mirroring of the IO Accelerators, as well as
off-server replication such as a Data Guard periodic backup.
2. Use the IO Accelerator-hosted ASM groups or filesystems like any other block device.
For more information on setting up this architecture, see "Generic Performance Tuning (on page 12)."
Hosting temp space on the IO Accelerator
This solution moves all temp space I/O off to local IO Accelerators while keeping the database and redo
log file areas on traditional storage devices.
Performance benefits, such as reduced query time, are seen most strongly in reporting or query-heavy
environments dealing with large datasets. These types of datasets include:
• High-volume OLTP applications
• Query-intensive data warehouses
• Demanding internet applications
This architecture might also benefit systems that are currently pushing their legacy storage near the limit.
The benefit comes by offloading all temp space I/O, which frees up additional headroom on the legacy
storage targets.
Example A: Migrating temp tablespace to an IO Accelerator on
a filesystem
For this example:
• All of the current database datafiles reside in the directory /u01/oradata/TESTDB
• Device /dev/md0 represents a RAID 0 configuration of the /dev/fioa and /dev/fiob IO
Accelerator devices
• /dev/md0 is configured to mount on /u02/oradata
Final Filesystem Configuration
To achieve the final filesystem configuration:
1. Change the ownership and permissions for the /u02/oradata directory to the following:
chown -R oracle.oinstall /u02/oradata