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 15:47] manu [Check performances on Spectrum Protect Client] |
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 101: | Line 111: | ||
dsmc sel c:\mydir\* -subdir=yes -enableinstrumentation=yes | dsmc sel c:\mydir\* -subdir=yes -enableinstrumentation=yes | ||
</cli> | </cli> | ||
+ | |||
+ | On older version of client, before 8.1 use the -TESTFLAG=instrument:detail,-TESTFLAG=instrument:API, and -TESTFLAG=instrumentation:detail/API options. | ||
**dsminstr.log** file is located in the directory that is specified by the DSM_LOG environment variable. You can also change the file name, location and size using **instrlogname** and **instrlogmax** options | **dsminstr.log** file is located in the directory that is specified by the DSM_LOG environment variable. You can also change the file name, location and size using **instrlogname** and **instrlogmax** options | ||
+ | Here is an example of statistics from dsminstr.log | ||
<code> | <code> | ||
Detailed Instrumentation statistics for | Detailed Instrumentation statistics for | ||
Line 140: | Line 153: | ||
----------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------- | ||
</code> | </code> | ||
+ | |||
+ | ==== Categories ==== | ||
+ | |||
+ | ^Category^Activity^ | ||
+ | |Query Server Dirs|Receiving the server inventory directories for incremental backup| | ||
+ | |Query Server Files|Receiving the server inventory files for incremental backup| | ||
+ | |Process Dirs|Scanning for files to back up| | ||
+ | |Cache Examine|Scanning the local disk cache database for files to expire| | ||
+ | |Solve Tree|Determining directory structure| | ||
+ | |Compute|Computing throughput and compression ratio| | ||
+ | |BeginTxn Verb|Building transactions Transaction File open, close, and other miscellaneous operations| | ||
+ | |File IO|File read and write| | ||
+ | |Compression|Compressing and uncompressing data| | ||
+ | |Encryption|Encrypting and decrypting data| | ||
+ | |CRC|Computing and comparing CRC values| | ||
+ | |Data Verb|Sending and receiving data to and from the server (points to the network or IBM Spectrum Protect server)| | ||
+ | |Confirm Verb|Response time during backup for server confirm verb| | ||
+ | |EndTxn Verb|Server transaction commit and tape synchronization (points to the IBM Spectrum Protect server)| | ||
+ | |Other|Everything else that is not tracked already| | ||
+ | |||