Database Page Set Timestamp Reset via Batch Write

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing database page writing techniques are inefficient, particularly when resetting timestamps, as they often require multiple writes for each page, leading to prolonged processing times and degraded performance.

Innovation Solution

Organizing database pages into logical page sets and issuing writes on a per-page-set basis, where all pages in a set are written once when the last page is updated, reducing the need for multiple write flags and flag releases, and allowing for parallel processing to enhance efficiency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If database pages are written individually with separate write flags, then each page can be tracked independently, but the time required to reset timestamps increases from hours to days

Engineering Contradiction:
Improvepage-level timestamp trackingVSAvoidtimestamp reset duration
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The patent merges multiple individual page write operations into a single batch operation by organizing pages into page sets. Instead of tracking and writing each page separately with its own write flag, the system groups pages and uses a single write flag at the page set level, thereby reducing the total number of write operations from days to hours while maintaining timestamp tracking accuracy.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent segments the database into page sets, where each page set contains multiple database pages. This segmentation allows the system to manage write operations at the page set level rather than individual page level, reducing the overhead of write flag management and enabling more efficient batch processing of timestamp resets.

Inventive Principle:
Principle #1Segmentation

2Reliability

If multiple write flags are used for each database page, then write operations can be tracked accurately, but the complexity of write management increases

Engineering Contradiction:
Improvewrite operation trackingVSAvoidwrite flag management
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent combines multiple write flags into a single write flag per page set. Instead of having one write flag for each individual page, the system uses one write flag to represent the entire page set, thereby reducing the number of flags that need to be managed while maintaining reliable tracking of write operations through the page set level.

Inventive Principle:
Principle #5Merging (Combining)

3Ease of operation

If database pages are written sequentially, then write operations are simple to manage, but parallel processing opportunities are lost

Engineering Contradiction:
Improvewrite operation managementVSAvoidtimestamp reset throughput
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The patent segments the database into independent page sets that can be processed in parallel. Each page set is an independent unit with its own pages and write flag, allowing multiple page sets to be written simultaneously by different threads or processes, thereby enabling parallel processing while keeping individual page set management simple.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces dynamic parallel processing capabilities by allowing multiple page sets to be written concurrently. The system can adaptively utilize available processing resources by launching multiple write operations in parallel across different page sets, thereby increasing throughput while maintaining operational simplicity through the page set abstraction.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS12067003B2Performance enhancement for writing database pages
Publication Date: 2024.08.20 SAP SE
  • US12067003B2 patent drawing
  • US12067003B2 patent drawing
  • US12067003B2 patent drawing

AI summary

A system and method including receiving a request to update a timestamp associated with database pages of a database instance logically organized into at least one page set, each of the at least one page set including a plurality of the database pages; updating the timestamp associated with each database page in each respective at least one page set; issuing, in response to updating the timestamp associated with a last database page in each of the at least one page set, a write request to write the plurality of database pages in each of the respective at least one page set to a persistent data store; and writing the plurality of database pages in each of the respective at least one page set to a persistent data store, the plurality of database pages written to the persistent data store having an updated timestamp associated therewith.