Coordinator Node Hot Page Execution for OLTP Cluster Efficiency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In online transaction processing (OLTP) clusters, high concurrency and intense conflicts lead to significant page transfer overheads, resulting in low transaction execution efficiency and poor database performance due to the need for frequent page transfers between coordinator nodes (CN) and data processing nodes (PN).
Innovation Solution
The method involves identifying 'hot pages' based on processing frequency and executing target operations on these pages directly by the CN, reducing the need for frequent page transfers by allowing CN to process operations that can be executed concurrently with the data processing nodes, thereby improving transaction execution efficiency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the CN obtains and transfers pages frequently between PNs and CN, then data consistency is maintained, but page transfer overhead increases and transaction execution efficiency decreases
Solution Approach 1:
The patent segments the transaction execution process into two parts: operations that can be executed locally by PNs and operations requiring CN involvement. By identifying and separating executable operations from page transfer operations, the system reduces unnecessary page transfers while maintaining data consistency through selective CN intervention.
Solution Approach 2:
The patent implements preliminary action by having PNs execute operations locally before needing page transfers. The CN pre-identifies which operations can be executed by PNs and which require page transfers, allowing PNs to perform local execution first and only transfer pages when absolutely necessary, thereby reducing overall transfer overhead.
2Productivity
If the CN executes target operations on hot pages, then page transfer overhead is reduced, but the complexity of operation routing and execution increases
Solution Approach 1:
The patent applies dynamics by making the execution location flexible rather than fixed. The system dynamically determines whether each operation should be executed by the PN or the CN based on real-time conditions such as operation type, page location, and current system state. This dynamic routing reduces the need for complex static routing tables while maintaining efficiency.
Solution Approach 2:
The CN acts as an intermediary that coordinates between multiple PNs and manages page transfers. By centralizing the decision-making logic for operation execution in the CN, the system simplifies the complexity distribution - the CN handles the routing complexity while PNs focus on execution, effectively managing overall system complexity through hierarchical coordination.
Data Source
Figure 1-1
Figure 1-2
Figure 2-1
AI summary
The present invention discloses a transaction execution method, apparatus, and system, and pertains to the computer field. The method is applied to a CN of an OLTP cluster database, and the method includes: receiving a page request message sent by a first PN, where the first PN has a first transaction configured, the first transaction includes at least one operation, and the page request message includes an identifier of a to-be-processed page and an identifier of the first PN; if the to-be-processed page indicated by the identifier of the to-be-processed page is the same as a hot page in a preset hot page set, determining a target operation corresponding to the to-be-processed page, where the preset hot page set includes at least one hot page; executing the target operation on the to-be-processed page to obtain an execution result; and sending the execution result to the first PN indicated by the identifier of the first PN, so as to resolve a problem that a transaction execution capability is relatively low and OLTP cluster database performance is relatively poor, so that the transaction execution capability and the OLTP cluster database performance are improved for transaction execution.