Protocol: FTP Bytes
This statistic shows FTP bytes/second requested by clients to Oracle ZFS Storage Appliance. Various useful breakdowns are available: to show the client, user, and filename of the FTP requests.
Example
FTP
When to Check FTP Bytes
FTP bytes/sec can be used as an indication of FTP load, and can be viewed on the dashboard.
The best way to improve performance is to eliminate unnecessary work, which can be identified through the client
, user
, and filename
breakdowns, and the filename hierarchy view. It might be best to enable these breakdowns for short periods only: The by-filename breakdown can be one of the most expensive in terms of storage and execution overhead, and might not be suitable to leave enabled permanently on appliances with high rates of FTP activity.
FTP Bytes Breakdowns
Table 5-39 Breakdowns of FTP Bytes
Breakdown | Description |
---|---|
type of operation |
FTP operation type (get/put/...). |
user |
Username of the client. |
filename |
Filename for the FTP operation, if known, and cached by Oracle ZFS Storage Appliance. If the filename is not known it is reported as <unknown>. |
share |
The share for this FTP request. |
project |
The project for this FTP request. |
client |
Remote hostname or IP address of the FTP client. |
These breakdowns can be combined to produce powerful statistics. For example, use Protocol: FTP bytes per second for client hostname.example.com broken down by filename
to view which files a particular client is accessing.
Further Analysis
See Cache: ARC Accesses to learn how well an FTP read workload is returning from cache, and Disk: I/O Operations for the back-end disk I/O caused.