Storage Access Timeline Visualization for Application Performance Optimization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Analyzing and visualizing storage access events in computing systems is challenging due to the complexity of storage input/output operations, which involve the file system and indirect actions by the application and operating system, making it difficult to trace and correlate storage access events with application performance.

Innovation Solution

A storage access timeline is constructed using event data gathered during execution, displaying storage access events alongside non-storage events like thread and processor events, allowing for a visual representation of storage access events and their correlation with application operations, enabling better understanding and optimization of storage access.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If storage input/output operations are performed through the file system service, then storage access functionality is provided, but it becomes difficult to trace and correlate storage access events with application performance

Engineering Contradiction:
Improvestorage access functionalityVSAvoidtraceability of storage access events
Core Design Contradiction:
Ease of operationVSDifficulty of detecting and measuring

Solution Approach 1:

The patent introduces an intermediary component that sits between the application and the file system service. This intermediary captures storage access events at the application level before they reach the file system, enabling direct correlation between application operations and storage access without disrupting the existing file system interface. The intermediary translates high-level application events into observable storage events, solving the traceability problem while maintaining ease of operation.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates a copy or representation of storage access events at the application level. Instead of trying to trace events through the complex file system service, the system generates duplicate event data that mirrors storage access operations. This copied event data can be directly correlated with application performance metrics, making detection and measurement straightforward while the original file system operations continue uninterrupted.

Inventive Principle:
Principle #26Copying

2Adaptability or versatility

If indirect actions by the application or operating system cause storage input/output, then storage access functionality is extended, but correlation to the application becomes difficult

Engineering Contradiction:
Improvestorage access coverageVSAvoidcorrelation capability
Core Design Contradiction:
Adaptability or versatilityVSDifficulty of detecting and measuring

Solution Approach 1:

The patent implements a feedback mechanism where the intermediary component continuously monitors application events and provides real-time information about storage access operations. When indirect actions occur (such as page faults or virtual memory operations), the feedback loop captures these events and correlates them back to the originating application actions. This creates a closed-loop system that maintains correlation capability despite the extended coverage of indirect storage access paths.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent performs preliminary action by establishing event correlation mappings before indirect storage actions occur. The intermediary component pre-configures tracking relationships between application events and potential storage operations. When indirect actions like page faults occur, the pre-established mappings enable immediate correlation without requiring complex real-time analysis, thus maintaining correlation capability across diverse storage access paths.

Inventive Principle:
Principle #10Preliminary action

3Measurement precision

If comprehensive event data is collected during execution, then analysis capability is improved, but system complexity increases

Engineering Contradiction:
Improveevent data collection accuracyVSAvoidsystem complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent segments the event data collection process into distinct, manageable components. The intermediary component divides event data into specific categories (storage access events, application events, timing information) and processes each segment separately. This segmentation allows comprehensive data collection without overwhelming system complexity, as each segment can be handled by dedicated, simple processing logic rather than a monolithic complex system.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent extracts only the essential event data needed for storage access analysis, rather than collecting all possible execution data. The intermediary component selectively captures storage-relevant events and filters out unrelated application events. This extraction approach maintains measurement precision for storage analysis while reducing system complexity by avoiding the overhead of comprehensive full-system instrumentation.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS8539171B2Analysis and timeline visualization of storage channels
Publication Date: 2013.09.17 MICROSOFT TECHNOLOGY LICENSING LLC
  • US8539171B2 patent drawing
  • US8539171B2 patent drawing
  • US8539171B2 patent drawing

AI summary

The visualization of a storage access on a timeline that represents various disk access events, such as a storage read event, or a storage write event. The storage access timeline may be formulated using event data gathered regarding storage access events, such as storage read requests, or storage write requests. The timeline may be displayed in conjunction with non-storage events, such as thread events, process events, processor events, or such, in order to give a visual indication of what is causing the storage access events. There may even be a control for displaying an identification of the file being accessed for one or more of the storage access events. With a better understanding of correlation between storage access events and application operation, optimization of the application itself may be achieved to more efficiently interface with the storage medium.