Page Comparison

TCP

Supported transport protocol (TCP/UDP | TCP | UDP)

80

Required. Network port for traffic to Swarm Storage nodes

9200

Required. Network port for traffic to Swarm Search nodes

sys 

Remote Procedure Call (RPC) security type (sys | krb5 | krb5i | krb5p)

100

Maximum number of open connections to Swarm Storage. (v2.0)

5

(positive integer) How many times SwarmFS will retry unsuccessful requests to Swarm and Swarm Search before giving up.

90

(seconds) How long SwarmFS will wait before timing out Swarm retries.

90

(seconds) How long SwarmFS will wait before timing out Swarm requests.

For best results, set this timeout to at least twice the value of the Storage setting scsp.keepAliveInterval.

300

(seconds) How long discovered Swarm storage nodes are remembered.

90

(seconds) How long SwarmFS will wait for a write to Swarm to complete before retrying.

128000000

(bytes) Defaults to 128 MB, for general workloads. The amount of data to be read each time from Swarm. If the read size buffer is larger than the client request size, then the difference will be cached by SwarmFS, and the next client read request will be served directly from cache, if possible. Set to 0 to disable read-ahead buffering.

Improving performance — Set each export's Read Buffer Size to match the workload that you expect on that share. 

• Lower the read-ahead buffer size if most reads will be small and non-sequential.

• Increase the read-ahead buffer size if most reads will be large and sequential.

4

(positive integer) Adjust to tune the performance of large object reads; the default of 4 reflects the optimal number of threads, per performance testing. (v2.3)

64000000

(bytes) How large each part of erasure-coded (EC) objects may be. Increase (such as to 200 MB, or 200000000) to create smaller EC sets for large objects and so increase throughput for high volumes of large files. (v2.3)

1000

(milliseconds) Increase to minimize object consolidation time by directing SwarmFS to collect more data before pushing it to Swarm, at the expense of both RAM and read performance, as SwarmFS slows clients when running out of cache. You might may increase this value if your implementation is sensitive to how quickly the Swarm health processor will consolidate objects, which cannot be guaranteed. (v2.3)

2000000000

(bytes) Defaults to 2 GB. Maximum limit that can be allocated for the export's export buffer pool. Once exceeded, client requests will temporary be blocked until total buffers falls back below this number. (v2.0)

1500000000

(bytes) Once the allocated export buffers reach this watermark, SwarmFS will start to free buffers in an attempt to stay below “Maximum Memory Buffers”. During this time, client requests may be delayed. (v2.0)

"relatime"

Policy for when to update a file's access time stamp (atime). (v2.0)

• “noatime”: Disables atime updates.

• “relatime”: Updates atime only if it is earlier than last modified time, so that it updates only once after each write.

• “strictatime”: Updates atime on every read and close.

60

(seconds) How rapidly non-SwarmFS object updates are reflected in SwarmFS listings. Lower to reduce the wait for consistency, at the cost of increased load on Elasticsearch. (v2.3)