Persistence Layer Page Linkage for Storage Efficiency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current data storage applications face inefficiencies in operations such as deletion, seeking, and prefetching due to the need to access and read multiple storage pages sequentially, which is resource-intensive and limits performance.

Innovation Solution

Retaining additional page data like page size and next page linkage at the persistence layer allows direct access and manipulation of storage pages without needing to access the entire sequence, enabling efficient deletion, seeking, and prefetching operations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If sequential access to storage pages is used for deletion, seeking, and prefetching operations, then data integrity is maintained, but input/output activity increases and performance decreases

Engineering Contradiction:
Improveoperation efficiencyVSAvoidinput/output activity
Core Design Contradiction:
ProductivityVSLoss of energy

Solution Approach 1:

The patent applies preliminary action by pre-computing and storing metadata (page sizes, next page linkages, page sequences) in the persistence layer before operations are needed. This allows deletion, seeking, and prefetching operations to directly access and manipulate storage pages using pre-prepared information, avoiding sequential scanning and reducing I/O activity significantly

Inventive Principle:
Principle #10Preliminary action

2Speed

If sequential access to storage pages is used, then simple data structure is maintained, but access time increases

Engineering Contradiction:
Improvepage access speedVSAvoidoperation time
Core Design Contradiction:
SpeedVSLoss of time

Solution Approach 1:

The system performs preliminary actions by organizing storage pages into sequences and pre-computing metadata including next page linkages and page sizes during the savepoint process. This preparation enables direct access to any page in the sequence without sequential traversal, dramatically improving access speed and reducing operation time

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces metadata (including page sequences, next page linkages, and page sizes) as an intermediary layer between the data storage application and the physical storage pages. This intermediary contains pre-computed navigation information that enables direct page access and manipulation, eliminating the need for sequential scanning and significantly reducing access time

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If additional page data is retained at the persistence layer, then direct access and parallel operations are enabled, but memory usage increases

Engineering Contradiction:
Improveoperation throughputVSAvoidmemory consumption
Core Design Contradiction:
ProductivityVSQuantity of substance

Solution Approach 1:

The patent applies segmentation by dividing the metadata storage into organized structures within the persistence layer, separating page sequences, next page linkages, and page size information into distinct data elements. This segmented organization allows efficient retrieval of specific metadata without loading entire page structures into memory, enabling direct access and parallel operations while controlling memory consumption

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS8615632B2Co-storage of data storage page linkage, size, and mapping
Publication Date: 2013.12.24 SAP SE
  • US8615632B2 patent drawing
  • US8615632B2 patent drawing
  • US8615632B2 patent drawing

AI summary

A logical page identity for a logical page containing data storage application data can be mapped to a physical storage page location in a storage where the data of the logical page are stored. The mapping as well as additional page data can be retained within a persistence layer accessible to the data storage application. The additional page data can include at least one of a size of the page and a next page linkage indicating a second page that follows the page in a page sequence of related pages. The retained mapping and additional page data can be retrieved from the persistence layer to initiate a page operation on the related pages, and the page operation can be executed on the related pages based on the retrieved mapping and additional page data. Related methods, systems, and articles of manufacture are also disclosed.