Oracle international corporation (20240126741). SYSTEM AND METHOD FOR INCREASED TRANSACTION THROUGHPUT AND IMPROVED RESPONSE TIME UNDER HIGH CONTENTION simplified abstract
Contents
- 1 SYSTEM AND METHOD FOR INCREASED TRANSACTION THROUGHPUT AND IMPROVED RESPONSE TIME UNDER HIGH CONTENTION
- 1.1 Organization Name
- 1.2 Inventor(s)
- 1.3 SYSTEM AND METHOD FOR INCREASED TRANSACTION THROUGHPUT AND IMPROVED RESPONSE TIME UNDER HIGH CONTENTION - A simplified explanation of the abstract
- 1.4 Simplified Explanation
- 1.5 Potential Applications
- 1.6 Problems Solved
- 1.7 Benefits
- 1.8 Potential Commercial Applications
- 1.9 Possible Prior Art
- 1.10 Original Abstract Submitted
SYSTEM AND METHOD FOR INCREASED TRANSACTION THROUGHPUT AND IMPROVED RESPONSE TIME UNDER HIGH CONTENTION
Organization Name
oracle international corporation
Inventor(s)
VASUDHA Krishnaswamy of Fremont CA (US)
DIETER Gawlick of Palo Alto CA (US)
TIRTHANKAR Lahiri of Palo Alto CA (US)
WEIWEI Gong of Belmont CA (US)
SYSTEM AND METHOD FOR INCREASED TRANSACTION THROUGHPUT AND IMPROVED RESPONSE TIME UNDER HIGH CONTENTION - A simplified explanation of the abstract
This abstract first appeared for US patent application 20240126741 titled 'SYSTEM AND METHOD FOR INCREASED TRANSACTION THROUGHPUT AND IMPROVED RESPONSE TIME UNDER HIGH CONTENTION
Simplified Explanation
The abstract describes a lock-free reservation mechanism in a database server where updates to reservable columns are not immediately locked but instead added to a reservation journal until the transaction commits. Constraint checks are performed before adding reservations to ensure data integrity.
- Lock-free reservation mechanism in a database server
- Updates to reservable columns are added to a reservation journal
- Lock is obtained and update is made at commit time
- Constraint checks performed before adding reservations
- Consider pre-existing reservations in the journal
Potential Applications
The technology can be applied in various database systems where concurrent transactions need to update reservable columns without immediate locking, ensuring data integrity and avoiding deadlocks.
Problems Solved
1. Avoids immediate locking of rows, reducing contention in high-concurrency environments. 2. Ensures data integrity by performing constraint checks before committing updates.
Benefits
1. Improved performance in high-concurrency environments. 2. Enhanced data integrity through constraint checks. 3. Avoidance of deadlocks by delaying locks until commit time.
Potential Commercial Applications
Optimizing database systems for high-concurrency environments Enhancing data integrity in transactional systems
Possible Prior Art
One possible prior art could be the use of optimistic concurrency control techniques in database systems to handle concurrent updates without immediate locking.
Unanswered Questions
How does the technology handle rollback scenarios?
The article does not mention how the system handles rollback scenarios where a transaction needs to be aborted after making reservations but before committing the updates.
What impact does the reservation mechanism have on system scalability?
The scalability implications of adding reservations to a journal and obtaining locks at commit time are not discussed in the abstract.
Original Abstract Submitted
a lock-free reservation mechanism is provided. when a transaction issues an update that affects a value in a “reservable column” of a row, the database server does not immediately obtain a lock that covers the row. instead, the database server adds a reservation to a reservation journal. at the time the transaction commits, a lock is obtained and the requested update is made. in one implementation, before adding the reservation to the reservation journal, the database server determines whether making the update would violate any constraints involving the reservable column. in one implementation, the constraint check not only takes into account the current value of the data item that is being updated and the amount of the update, but also pre-existing reservations in the reservation journal that affect the same data item.