This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
tsm:tsm_perf [2021/01/18 16:25] manu [Categories] |
tsm:tsm_perf [2023/11/06 10:14] (current) manu |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| Are you in the best practice for the server ? | Are you in the best practice for the server ? | ||
| * have a look on Spectum Blueprint (on google) | * have a look on Spectum Blueprint (on google) | ||
| + | |||
| + | ===== Spectrum Protect Server block size considerations ===== | ||
| + | |||
| + | DB block size used: 8kb\\ | ||
| + | Storage pool DISK and FILE: reads and writes to storage pools predominantly in **256 KB** blocks\\ | ||
| + | The extents can range in size from 50 KB to 4 MB with an average of 256 KB. Any data smaller than 2 KB or data that cannot be deduplicated, such as encrypted or compressed, are not deduplicated. | ||
| + | |||
| + | S3: By default, these files are 1 GB in size and are configurable using the parameter | ||
| + | CloudTransferContainerSize server option (i.e. specifying in dsmserv.opt or using the “setopt” server command). These files are transferred to Access using S3 multipart-upload. With 1 GB default file size, the default part size that the file is broken up to is 100 MB. | ||
| + | This value is configurable using the server parameter, CloudMinUploadPartSize. For restores, IBM Spectrum Protect does range reads in smaller sizes of 10 KB – 100KB | ||
| ===== Check performances on Spectrum Protect Server ===== | ===== Check performances on Spectrum Protect Server ===== | ||
| Line 162: | Line 172: | ||
| |EndTxn Verb|Server transaction commit and tape synchronization (points to the IBM Spectrum Protect server)| | |EndTxn Verb|Server transaction commit and tape synchronization (points to the IBM Spectrum Protect server)| | ||
| |Other|Everything else that is not tracked already| | |Other|Everything else that is not tracked already| | ||
| + | |||