Client-Side Performance Metrics Collection via Browser Reporting
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Content providers cannot measure client-side latencies and performance metrics, limiting their ability to monitor and report on the rendering of web-based content at user computing devices.
Innovation Solution
Implementing a system where browser applications collect and transmit performance measures, such as rendering times and event counters, to a reporting service module, which aggregates and stores this data in a database for performance monitoring and reporting.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If content providers only measure server-side latencies, then server performance monitoring is simple and direct, but client-side performance metrics remain unknown and unmeasurable
Solution Approach 1:
The patent introduces a reporting service module as an intermediary between the browser application and the content provider's server. This mediator collects performance data from the browser, validates it, and transmits it to the server, enabling client-side measurement without requiring direct server-client performance monitoring infrastructure
Solution Approach 2:
The measurement system is divided into separate functional components: a browser application that collects client-side metrics, a reporting service module that validates and transmits data, and a server that aggregates and stores performance information. This segmentation allows each component to specialize in specific measurement tasks
2Loss of information
If browser applications collect and transmit performance data, then client-side metrics become measurable, but network bandwidth and server storage requirements increase
Solution Approach 1:
The system collects only specific performance metrics that are most relevant to web page rendering and delivery, rather than attempting to measure all possible system parameters. The reporting service validates and filters data to ensure quality over quantity
Solution Approach 2:
The collected performance data is fed back to the content provider's server, creating a closed-loop system where measurement results inform future content delivery decisions, enabling continuous optimization of web page performance
Data Source
AI summary
Technologies are described herein for collecting client-side performance metrics and latencies. A web page received by a web browser application executing on a user computing device includes markup or scripting code that instructs the browser to collect performance measures during the rendering of the content of the web page. The performance measures may include operation timings that measure the time it takes for a particular operation to complete during the rendering of the content and/or event counters that count the number of times that a specific event occurs during the rendering of the content. The web browser application sends an event report containing the collected performance measures to a reporting module executing on a server computer. The reporting module receives the event report, validates the content of the event report, and adds the event report to a database or other data storage system.