Server Latency Determination via Scripted Measurement

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing web page rendering is delayed due to synchronous content item retrieval, making it difficult to identify and calculate latency times associated with multiple content servers, especially when one server is slow or inoperable.

Innovation Solution

A system and method to determine latency times by specifying URLs with arguments to execute scripts that measure publisher server, first content server, and second content server performance, allowing for the calculation of latency times and displaying this information to users.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If synchronous content item retrieval is used, then content items are received and processed in order, but web page rendering is delayed when content servers are slow

Engineering Contradiction:

Improvecontent item retrieval reliabilityVSAvoidweb page rendering time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent segments the content item retrieval process by introducing unique identifiers and timestamps for each content request. This allows the system to track and measure latency for individual content items from different servers, enabling selective optimization without compromising overall rendering reliability

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary measurement mechanism that captures request and response timestamps without disrupting the synchronous retrieval flow. This intermediary layer records latency data while allowing the original content retrieval process to continue, thus maintaining reliability while providing timing information for optimization

Inventive Principle:

Principle #24Intermediary (Mediator)

2Measurement precision

If synchronous content item processing is used, then content items are processed in order, but calculating latency times becomes complex due to multiple HTTP requests and responses

Engineering Contradiction:

Improvelatency time measurement accuracyVSAvoidlatency calculation complexity

Core Design Contradiction:

Measurement precisionVSDevice complexity

Solution Approach 1:

The patent applies preliminary action by embedding unique identifiers and timestamp markers in content requests before they are sent to servers. This pre-prepared measurement framework simplifies subsequent latency calculation, as the data needed for accurate measurement is already captured in the request-response cycle without requiring complex post-processing

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent implements feedback by using recorded latency data to inform future content retrieval decisions. The system feeds back latency information about different content servers to optimize future request routing, creating a closed-loop system that continuously improves performance based on measured data

Inventive Principle:

Principle #23Feedback

Data Source

PatentUS8949405B2Content server latency determination

Publication Date: 2015.02.03 GOOGLE LLC

AI summary

A performance of a publisher server, a first content server, and a second content server is determined. Latency time information is determined based on the publisher server performance, the first content server performance, and the second content server performance, the latency time information representing a length of time to load content associated with each of the publisher server, the first content server, and the second content server.