Browser Performance Monitoring Code for Accurate Response Time Benchmarking

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing web service performance monitoring systems either introduce additional delays by interposing components between client devices and application servers or approximate response times, failing to accurately determine the actual response time experienced by users.

Innovation Solution

A benchmark response time is determined by performance monitoring code loaded into the browser application, which automatically sends requests to a network server, processes randomly generated data, and records processing times, maintaining constants to compute and compare response times effectively.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If an interposed component is added between client device and application server to monitor performance, then performance monitoring capability is improved, but communication delay increases

Engineering Contradiction:

Improveperformance monitoring capabilityVSAvoidcommunication delay

Core Design Contradiction:

Measurement precisionVSLoss of time

Solution Approach 1:

The monitoring function is extracted from the communication path by using client-side scripting code that executes in the browser. This removes the need for an interposed monitoring component in the server-client communication path, eliminating the additional delays while preserving the ability to measure response times accurately.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The client device performs self-monitoring by executing performance monitoring code locally in the browser. The client automatically captures response times and sends this data to the server without requiring manual intervention or additional server-side monitoring infrastructure, thus avoiding communication delays caused by interposed components.

Inventive Principle:

Principle #25Self-service

2Ease of manufacture

If server-side time capture is used to monitor web service performance, then monitoring implementation is simplified, but measurement accuracy deteriorates due to approximations

Engineering Contradiction:

Improvemonitoring implementation simplicityVSAvoidresponse time accuracy

Core Design Contradiction:

Ease of manufactureVSMeasurement precision

Solution Approach 1:

Instead of having the server measure response times (server-side time capture), the client device is empowered to measure its own response times by executing performance monitoring code. This inversion of the measurement perspective provides accurate client-experienced response times while maintaining implementation simplicity through automated client-side execution.

Inventive Principle:

Principle #13The other way round (Inversion)

Solution Approach 2:

The mechanical server-side measurement system is replaced with an automated client-side software-based measurement system. The performance monitoring code executes automatically in the browser environment, capturing accurate response times without requiring complex server-side instrumentation or approximation calculations.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

3Measurement precision

If automatic benchmark requests are sent by the browser application, then user interaction delays are eliminated, but network traffic increases

Engineering Contradiction:

Improveresponse time measurement accuracyVSAvoidnetwork traffic

Core Design Contradiction:

Measurement precisionVSQuantity of substance

Solution Approach 1:

The performance monitoring uses simplified copy requests that replicate only the essential benchmarking functionality. Instead of full user interactions, the system uses streamlined HTTP requests that capture response times without the overhead of complete user workflows, reducing network traffic while maintaining measurement accuracy.

Inventive Principle:

Principle #26Copying

Data Source

PatentUS8849981B2Response time benchmarking

Publication Date: 2014.09.30 CA TECH INC

AI summary

A benchmark response time is determined for a browser application request sent to a network server over a network. The response time is determined by performance monitoring code that is loaded into and monitors the browser application from the client. The performance monitoring code automatically sends a request to a network server; the request is not sent in response to user input. The network server receives the request, generates a response and provides the response to the browser application. The response includes a fixed amount of randomly generated data. The browser application receives and processes the response, but does not display the bytes or change the content displayed in the browser application as a result of the response. The browser application sends the times at which the browser application sends the request and the browser application completes processing the response data to the network server for further processing.