DBMS Da
DBMS Da
Online Transaction Processing (OLTP) systems are the backbone of modern data-driven applications, powering
everything from e-commerce platforms and banking systems to social media and cloud services. Designed to handle a
high volume of short transactions that update shared data, these systems face increasing challenges in maintaining
efficient and reliable performance as their complexity and scale grow. One of the primary challenges in OLTP systems
is managing transaction conflicts, which occur when multiple transactions attempt to access and modify shared data
concurrently, risking data inconsistencies and system failures. To address this issue, various transaction scheduling
techniques—such as two-phase locking and timestamp-based protocols—have been developed. While these
approaches are effective in certain contexts, they often encounter limitations, including performance overhead and
difficulties in managing complex workloads.
Data inconsistency or Deadlocks: Incorrect data values may be written to the database if
transactions are not properly synchronized. A deadlock occurs when two or more transactions are
waiting for eachother to release resources, resulting in a stalemate.
Performance degradation: Transaction conflicts can significantly degrade system performance, leading to
increased response times and reduced throughput.
Quantifying the impact of transaction conflicts is crucial for assessing the effectiveness ofdifferent scheduling
techniques. Key metrics include:
Transaction abort rate: The percentage of transactions that are aborted due toconflicts or other reasons.
1.3 Research Gap
Traditional transaction scheduling techniques, such as two-phase locking and timestamp-based protocols, often rely
on pessimistic approaches that assume the worst-case scenario.These techniques can lead to excessive locking and
contention, deleting system performance. There is a growing need for more intelligent and adaptive transaction
scheduling techniques to address these limitations. These techniques should be able to:
The following steps are involved in building the conflict prediction model:
1. Feature Engineering:
o Identify relevant features that can be used to predict conflicts, such as transaction size, resource
requirements, historical conflict patterns, andworkload characteristics.
o Apply feature engineering techniques, such as normalization, scaling, and feature selection, to
improve model accuracy and efficiency.
o Train the selected model on a large dataset of historical transaction data,using techniques such as
cross-validation to prevent overfitting.
3. Model Evaluation:
o Assess the performance of the trained model using appropriate metrics,such as accuracy,
precision, recall, and F1-score.
1. Priority-Based Scheduling:
o Prioritize high-priority transactions for execution to minimize response time and improve system
throughput.
2. Resource Allocation:
3. Conflict Resolution:
PAGE 4
Page 4: Conclusion and Future Work
4.3 References
1. https://doi.org/10.48550/arXiv.2409.01675
2. https://doi.org/10.1109/ICOEI48184.2020.9143025
3. https://doi.org/10.1109/TII.2022.3169457
4. https://doi.org/10.1109/ACCESS.2020.3017694
PAGE 5