Async Operation Load Time Accuracy via Repeating Pattern Removal

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing methods for determining user interface load times are inaccurate due to the inclusion of repeating async operations, which can create miscalculations by continuously reloading and making it appear that the interface has not completed loading.

Innovation Solution

A system comprising a monitor engine, detection engine, removal engine, and calculation engine that identifies and removes repeating async operations, calculates the total load time based on the greatest end time of non-repeating async operations, and bubbles up completed operations to a parent loader, providing a more accurate user interface load time.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If repeating async operations are included in load time calculation, then the calculation covers all operations, but the load time becomes inaccurate due to continuous reloading

Engineering Contradiction:

Improveload time measurement accuracyVSAvoidoperation monitoring and filtering complexity

Core Design Contradiction:

Measurement precisionVSDevice complexity

Solution Approach 1:

The patent extracts and removes repeating async operations from the load time calculation set. The detection engine identifies operations that continuously reload and excludes them from the final load time measurement, thereby improving accuracy without requiring complete abandonment of comprehensive monitoring

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces intermediate engines (detection engine, removal engine) that act as mediators between the comprehensive operation monitoring system and the final load time calculation. These intermediaries filter out repeating operations while allowing non-repeating operations to pass through to the calculation engine

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If all async operations are monitored to calculate total load time, then comprehensive coverage is achieved, but repeating operations cause miscalculation by making interface appear not loaded

Engineering Contradiction:

Improveload time calculation reliabilityVSAvoidtime spent identifying and removing repeating operations

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The detection engine performs preliminary identification of repeating async operations before they affect the load time calculation. By detecting and flagging repeating operations in advance, the system prevents them from causing miscalculations rather than correcting them after the fact

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms where the detection engine continuously monitors async operations and provides feedback to the removal engine about which operations are repeating. This feedback loop ensures that only non-repeating operations contribute to the final load time measurement

Inventive Principle:

Principle #23Feedback

Data Source

PatentUS9996443B2User action duration

Publication Date: 2018.06.12 MICRO FOCUS LLC

AI summary

In one implementation, a system for user action duration includes a monitor engine to monitor a number of async operations to be loaded on a user interface, a detection engine to determine a repeating async operation from the number of async operations that has a pattern of repeating timeouts, a removal engine to remove the repeating async operation from the number of async operations, and a calculation engine to calculate a total time for the remaining number of async operations based on a total timeout of each of the remaining number of async operations.