Oracle 5.0 Reference Manual page 553

The number of SSL session cache misses.
•
Ssl_session_cache_mode
The SSL session cache mode.
•
Ssl_session_cache_overflows
The number of SSL session cache overflows.
•
Ssl_session_cache_size
The SSL session cache size.
•
Ssl_session_cache_timeouts
The number of SSL session cache timeouts.
•
Ssl_sessions_reused
How many SSL connections were reused from the cache.
•
Ssl_used_session_cache_entries
How many SSL session cache entries were used.
•
Ssl_verify_depth
The verification depth for replication SSL connections.
•
Ssl_verify_mode
The verification mode for replication SSL connections.
• [533]
Ssl_version
The SSL protocol version of the connection.
•
Table_locks_immediate
The number of times that a request for a table lock could be granted immediately.
•
Table_locks_waited
The number of times that a request for a table lock could not be granted immediately and a wait was
needed. If this is high and you have performance problems, you should first optimize your queries,
and then either split your table or tables or use replication.
•
Tc_log_max_pages_used
For the memory-mapped implementation of the log that is used by
the transaction coordinator for recovery of internal XA transactions, this variable indicates
the largest number of pages used for the log since the server started. If the product of
Tc_log_max_pages_used
than the log size, the size is larger than necessary and can be reduced. (The size is set by the
[413]
log-tc-size
recovery, and the memory-mapped recovery log method is not used unless the number of storage
engines capable of two-phase commit is greater than one.
Added in MySQL 5.0.3.
•
Tc_log_page_size
Server Status Variables
[533]
[533]
[533]
[533]
[533]
[533]
[533]
[533]
[533]
[533]
[533]
[533] and
Tc_log_page_size
option. Currently, this variable is unused: It is unneeded for binary log-based
[533]
533
when it acts as
mysqld
[533] is always significantly less
(InnoDB is the only applicable engine.)
--