Protocol: OISP Operations

Language:

This statistic shows OISP operations/sec requested by clients to the appliance. Operations statistics can be broken down by client, filename, database name, database filetype, database function, share, project, latency, size, and offset.

When to Check OISP Operations

OISP operations/sec can be used as an indication of OISP load, and can be viewed on the dashboard.

Breakdowns by database filetype and function allow database and storage administrators to correlate database statistics with storage statistics. This provides much better diagnosability to narrow down an abrupt rise not only to a particular database, but also to the database function creating the increase and the filetype associated with it.

Use the latency breakdown when investigating OISP performance issues, especially to quantify the magnitude of the issue. This measures the I/O latency component for which the appliance is responsible, and displays it as a heat map so that the overall latency pattern can be seen, along with outliers. If the OISP latency is high, drill down further on latency to identify the type of operation and filename for the high latency, and check other statistics for both CPU and disk load to investigate why the appliance is slow to respond. If latency is low, the appliance is performing quickly, and any performance issues experienced on the client are more likely to be caused by other factors in the environment, such as the network infrastructure, and CPU load on the client itself.

The best way to improve performance is to eliminate unnecessary work, which may be identified through the client and filename breakdowns, and the filename hierarchy view. Client and especially filename breakdowns can be very expensive in terms of storage and execution overhead. Therefore, it is not recommended to permanently enable these breakdowns on a busy production appliance.

OISP Operations Breakdowns

Table 46 Breakdowns of OISP Operations

Breakdown	Description
client	Remote hostname or IP address of the OISP client.
filename	Filename for the OISP I/O, if known and cached by the appliance.
database name	Name of the database issuing the I/O.
database filetype	Type of file to which the database is writing.
database function	Reason for the database I/O. Acronyms used in this breakdown include RMAN (Oracle Recovery Manager), DBWR (Database Writer for Oracle Database), ARCH (Archiver for Oracle Database), and LGWR (Log Writer for Oracle Database).
share	The share for this OISP I/O.
project	The project for this OISP I/O.
latency	A heat map showing the latency of OISP I/O, as measured from when the OISP request arrived on the appliance from the network, to when the response is sent. The latency includes the time to process the OISP request, and to perform any disk I/O.
size	A heat map showing the distribution of OISP I/O sizes.
offset	A heat map showing the file offset of OISP I/O. This can be used to identify random or sequential OISP.

These breakdowns can be combined to produce powerful statistics. For example:

“Protocol: OISP operations per second for file ‘/export/fs4/10ga’ broken down by offset” (to examine file access pattern for a particular file)
“Protocol: OISP operations per second for client ‘phobos.sf.fishpong.com’ broken down by filename” (to view which files a particular client is accessing)

Further Analysis

Also see Protocol: Protocol: OISP Bytes.