Lock Tree

You can analyze the trend of locks during the day. The session that caused a lock (Lock Holder) and the session waiting for a lock (Lock Waiter) can be checked through a tree structure. Through these functions, you can analyze queries by checking the relationship between holders and waiters for locks that occurred at specific points.

Home > Select Project > Analysis > Lock Tree

It provides the time series chart and lock tree for the locks occurred during the day. From the point where a lock first occurred, the structure of holders and waiters is displayed in a tree form. You can check the rock tree over time.

• Visual lock trend by time: Through the 1-Min Lock Trends and Lock Wait Sessions features, the lock occurrence data can be analyzed in time zones.

Basic usage guide

Select the desired date, time, and instance to view in Time and Instance. If a lock occurs at the set time, the searched data appears in Lock Wait Sessions and the Lock Tree table at the bottom of the screen.

• You can see the data for up to two weeks within a chart. If you click a specific time in the graph chart, you can check the lock information for the selected time in the table at the bottom of the screen. If you select the button in seconds, you can view the lock information in 5-second increments.

  Note

  Through the tags on the upper right of the Lock Wait Sessions chart, you can see the units to view.

• As you continuously drag (drill down) a specific time zone on the graph chart, you can see the charts and lock trees for detailed time zones.

• You can see the data in 5-second increments by dragging within 3 hours on the chart. However, the data in 5-second increments can only be viewed within the most recent month. The data earlier than one month can only be viewed as 5-minute summary data. For example, you can drag (drill down) lock tree data from 40 days ago for the 5-minute summary data, but you cannot see 5-second data.

Lock Wait Sessions

The Lock Wait Sessions feature allows you to analyze the lock wait sessions. Depending on the query period, the lock wait session data is provided at 5-minute intervals when the query is for 3 hours or more, and at 5-second intervals when the query is for less than 3 hours. You can also adjust the time range by dragging the chart flexibly.

1-Min Lock Trends

If you click a specific time zone in Lock Wait Sessions, the lock occurrence status for 30 minutes, from 15 minutes before to 15 minutes after is visualized. This allows you to effectively analyze the lock occurrence trend at 30-minute intervals.

Note

Total Locks indicates the total number of locks generated in the time zone.

Viewing time

1-Min Lock Trends and Lock Tree tables are timed based on the maximum number of locks that occurred at the clicked time in Lock Wait Sessions. This allows you to find the zone with the most locks.

If you click the bar of a different time zone in the 1-Min Lock Trends chart with the Lock Wait Sessions unchanged, the time range is synced to the Lock Tree table by using the seconds with the highest number of locks for the minute. This allows you to see the information reflected in the Lock Tree table when changing the time zone.

• Viewing for 3 hours or more (using 5-minute data)

  The bar color of the 5-minute zone from the time of inquiry appears more prominent.

  When the 07:15:00 time point is clicked, the color of the 07:15:00-07:20:00 zone's bar chart appears more prominent.

  

• Viewing for less than 3 hours (using 5-minute data)

  It is useful for analyzing the locks that occur within short time intervals.

  

Active session

Item	Description
Instance Name	Instance Name
id	Connection identifier
user	SQL execution account
host	Hostname that this thread is connected to.
db	Default database name. If nothing, it is NULL.
command	Running command type (Query/Sleep/Daemon, etc.)
time	Execution time of the current command (sec)
state	Current thread status (executing, updating, sending data, etc.)
query	Running statement. It displays the literal value SQL separated from Processlist.info.
query_param	Literal value separated from query
type	Thread type. FOREGROUND/BACKGROUND, etc.
connection_type	The protocol used to establish a connection. TCP/IP, SSL/TLS

Lock tree

Item	Description
holder type	Type of the holder session
lock mode	holder_mode
waiter type	Type of the waiter session
lock request	waiter_mode
state	This is the step where the current process is in progress.
table	holder_table/waiter_table
index	holder_index/waiter_index

Process information

The following items are the metrics collected if the XOS agent has been installed.

Item	Description
cputime	CPU usage time
cpuusage	CPU Utilization
elapse	Elapsed time of CPU usage
vsize	Virtual memory size (Kb)
rss	Resident Set Size (RSS) that is the number of physical pages associated with the process.
state	Process status
ioread	Actual time spent reading the block (milliseconds)
iowrite	Actual time spent writing the block (milliseconds)
pss	Process specific memory usage + Percentage of shared memory occupied by one process
uid	user id
cmd	Executing command
longcmd	Full path of cmd

Analyzing with AI

Click the WhaTap AI button on the screen to open the WhaTap AI chat window, where the queried screen data is summarized and the analysis result is shown as a conversation. After reading the result, you can continue with follow-up questions in the same conversation.

• The data used for the analysis is three sets: the trend for the whole query range, the 30-minute interval aggregation, and the lock tree snapshot at the selected point in time.

• The analysis target is the data queried on the screen. If you change the query conditions and analyze again, the analysis is based on the changed data.

• The conversation history is recorded in the AI Analysis - {screen name} format.