JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris 11.1 Tunable Parameters Reference Manual     Oracle Solaris 11.1 Information Library
search filter icon
search icon

Document Information

Preface

1.  Overview of Oracle Solaris System Tuning

2.  Oracle Solaris Kernel Tunable Parameters

3.  Oracle Solaris ZFS Tunable Parameters

Where to Find Tunable Parameter Information

Tuning ZFS Considerations

ZFS ARC Parameters

zfs_arc_min

zfs_arc_max

ZFS File-Level Prefetch

zfs_prefetch_disable

ZFS Device I/O Queue Depth

zfs_vdev_max_pending

Tuning ZFS When Using Flash Storage

Adding Flash Devices as ZFS Log or Cache Devices

Ensuring Proper Cache Flush Behavior for Flash and NVRAM Storage Devices

SCSI Unmap Considerations for Flash Devices

Tuning ZFS for Database Products

Tuning ZFS for an Oracle Database

Using ZFS with MySQL Considerations

4.  NFS Tunable Parameters

5.  Internet Protocol Suite Tunable Parameters

6.  System Facility Parameters

A.  Tunable Parameters Change History

B.  Revision History for This Manual

Index

ZFS ARC Parameters

This section describes parameters related to ZFS ARC behavior.

zfs_arc_min

Description

Determines the minimum size of the ZFS Adaptive Replacement Cache (ARC). See also zfs_arc_max.

Data Type

Unsigned Integer (64-bit)

Default

64 MB

Range

64 MB to zfs_arc_max

Units

Bytes

Dynamic?

No

Validation

Yes, the range is validated.

When to Change

When a system's workload demand for memory fluctuates, the ZFS ARC caches data at a period of weak demand and then shrinks at a period of strong demand. However, ZFS does not shrink below the value of zfs_arc_min. Generally, you do not need to change the default value.

Commitment Level

Unstable

Change History

For information, see zfs_arc_min.

zfs_arc_max

Description

Determines the maximum size of the ZFS Adaptive Replacement Cache (ARC). See also zfs_arc_min.

Data Type

Unsigned Integer (64-bit)

Default

75% of memory on systems with less than 4 GB of memory

physmem minus 1 GB on systems with greater than 4 GB of memory

Range

64 MB to physmem

Units

Bytes

Dynamic?

No

Validation

Yes, the range is validated.

When to Change

If a future memory requirement is significantly large and well defined, you might consider reducing the value of this parameter to cap the ARC so that it does not compete with the memory requirement. For example, if you know that a future workload requires 20% of memory, it makes sense to cap the ARC such that it does not consume more than the remaining 80% of memory.

Commitment Level

Unstable

Change History

For information, see zfs_arc_max .