Workflows

Edit online

Writing an object
Writing an Object to PSS works exactly like FSS. Writes are completed in three phases: write, commit, and finalize.
Reading a slice
Deleting a slice
Listing a slice
All slice names are stored in the Catalog. Any list operations request the slice names from the Catalog and return the requested values.
Compacting a bin file
Some write (if overwriting a bin is required) and delete operations remove references to the affected bin, making the contained data inaccessible. The unreferenced bin still occupies space in a bin file. The process of removing unreferenced bins from bin files is called compaction. It is executed in the background without disrupting regular storage functions. Compaction occurs more frequently when disk utilization is close to 100% to reclaim unused space more quickly.
Improved performance with small objects
PSS has advantages over FSS as it uses a predictable access pattern to store and retrieve data.
Deploying to new storage pools only
PSS can be deployed on new storage pools only. All vaults sharing a PSS-enabled pool would have relevant slices stored in PSS. There is no mechanism to grant PSS access on the vault level. PSS improves performance and improves disk space utilization when used in CSO mode with large number of objects under 10 MB in size. The impact is especially significant when system load is dominated by objects smaller than 100 KB. PSS could improve latency even for large objects when storage pools have a variety of object sizes.

Parent topic: Packed Slice Storage