Think about what data you need to store on the MSS. Be selective, don't store data indiscriminately just because the MSS is there. In particular, temporary data (i.e. files with a lifetime of less than one month) should probably never be placed on the MSS.

Store fewer large files instead of numerous small files. Files smaller than 64 KB are very inefficient due to overhead, and a one byte file requires 112,640 bytes on the storage medium due to the blocking and checksum overheads, and you will be charged for all 112,640 bytes. Using the tar or cpio command to containerize existing sets of small files before transferring them to the MSS will also reduce the latency to read or write the small files.

Make use of single copies via Class of Service when the data doesn't require the highest level of reliability (see msclass(1NCAR) for details). Remember that the default reliability class of service generates dual copies, and that you will therefore be charged double as well.

Avoid repetitious reads if it all possible. For data that you will access frequently, cache it elsewhere.

Set a reasonable retention period when the MSS file is first created by using the -period option for msrcp(1NCAR) Try to estimate the useful lifetime of your data. For example, some data may only be useful while a specific type of computer is in use. In this case, a 5 year retention period (or the expected life of that computer) might be best. You can always change the retention period later if circumstances warrant it.