Sybase Performance Diagnostics Sp_sysmon Transaction Management

This article describes the adaptive server system through the Sp_sysmon of the operation of a comprehensive system to understand, is conducive to better understanding of system performance, more effective system management, rational use and allocation of system resources, to achieve system performance tuning purposes.

Learn from 18 aspects of the performance of the system and use environment parameters to tune performance when appropriate:

1, kernel Management (kernal) 2, Application Management (APPMGMT) 3, data cache management (Dcache)

4, ESP management (ESP) 5, index management (INDEXMGMT) 6, lock management (locks)

7, Memory Management (memory) 8, metadata cache Management (Mdcache) 9, Task management (TASKMGMT)

10, monitor access to the implementation of SQL (monaccess) 11, network I/O management (netio)

12. Parallel query Management (parallel) 13, process cache Management (Pcache) 14, Recovery Management (recovery)

15, transaction Management (XACTMGMT) 16, transaction profile (Xactsum) 17, disk I/O management (Diskio)

18. Work Process Management (WPM)

The English short word after parentheses is the module parameter.

Environment: 1, the user database has the data table auths and article for practice

2, the data table has 100,000 rows of data

3, the user has the query, the modification, the deletion and so on basic database table Operation Authority

Step: Perform Sp_sysmon "00:10:00" (server-level system storage process, no need to open a database), or perform the following format process to view the specific operation batch command corresponding to the system performance:

Sp_sysmon Begin_sample

SQL statement or storage process

Sp_sysmon Commit_sample

This experiment uses Sp_sysmon "HH:MM:SS", the performance module name.

Conclusion: Through this exercise, we can understand the current system in various aspects of the system operating conditions, performance problems and imbalance imbalance, learn to use the corresponding parameters and measures to solve and tune, and constantly compare the performance before and after adjustment, and ultimately improve system performance.

Note: 1, the command execution result set at the beginning of the same as the following, the block exercise is no longer one by one listed:

======================================================================

Sybase Adaptive Server Enterprise System Performance

======================================================================

Server version:adaptive Server Enterprise/11.9.2/1031/p/nt (IX86)/os 3.

Server Name:server is unnamed

Run Date:may 28, 2001

Statistics cleared at:15:57:27

Statistics sampled at:16:07:28

Sample interval:00:10:00

2, the implementation of the result set of each column information tip:

Per sec: average of each second during sampling

Per XACT: average of each transaction submitted during sampling

Count: Total value per second during sampling

% of total: percentages, depending on different circumstances

3, the result set corresponding to the performance of the description, analysis and tunable description

4, this exercise only gives some of the module monitoring results (may have deletions), with Sp_sysmon "HH:MM:SS" can see all the details.

Transaction management

Command line: Sp_sysmon "00:10:00", XACTMGMT

Results:

Transaction Management (transaction Management)

----------------------

User log cache (one per user) reduces the number of writes to the transaction log, which improves performance if multiprocessor systems also reduce contention on the current page of the transaction log. Configurable environment parameter "user log cache Size" (default minimum 2048 bytes), too small cause user log is often full and frequently write to the transaction log, too large, each connection user is enlarged, and cause memory waste. The principle is that the configuration does not exceed the length of the transaction completion write transaction log.

ULC flushes to Xact Log per sec/Xact count% of total

The number of times that various types caused the transaction log to be written

-------------------------  ------------  ------------  ----------  ----------

By full ULC 0.0 0.0 0 0.0%

If the value of% of total is more than 20%, consider increasing the value of the environment parameter "user log cache Size".

By End Transaction 11.8 1.0 7095 95.5%

The transaction ends with an explicit or implicit rollback or commit token. A large value indicates a lot of short business.

By change of Database 0.0 0.0 12 0.2

If the value is large, consider reducing the buffer pool larger than 2K in the ULC, reducing or removing large chunks of I/O pool.

by System Log 0.5 0.0 321 4.3%

The% of total value is greater than 20% and the ULC length is greater than 2048, considering reducing the length of the ULC.

By the other 0.0 0.0 0 0.0%

-------------------------  ------------  ------------  ----------

  Total ULC flushes                   12.4           1.1         7428