Concurrent Web Page Content Loading to Reduce Latency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Web pages often experience latency due to the delay in retrieving session-related data from remote servers, which can lead to impatient users navigating away, resulting in lost business opportunities as content loading times increase with the complexity of online shopping and service delivery.
Innovation Solution
Concurrent processing of non-session-related and session-related content allows for the reduction of page loading latency by determining and sending non-session-related content independently of session validation and data retrieval, thereby overlapping these operations in time.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Manufacturing precision
If session-related data is retrieved from remote servers before generating web page content, then content accuracy and personalization are improved, but page loading time increases
Solution Approach 1:
The system performs session validation and data retrieval operations in parallel with content generation operations. Specifically, the server validates the session identifier and retrieves session data concurrently with determining non-session-related content, so that when content generation completes, session data is already available or nearly available, reducing the overall waiting time for the user.
Solution Approach 2:
The content generation process is divided into independent segments: non-session-related content determination and session-related content determination. These segments are executed in parallel where possible, with non-session content being processed independently of session validation, allowing the system to make progress on multiple fronts simultaneously without requiring sequential completion of each step.
2Reliability
If session validation and data retrieval are performed sequentially before content generation, then data consistency is ensured, but processing efficiency decreases
Solution Approach 1:
Session validation is initiated as a preliminary action concurrent with content generation rather than waiting for content generation to complete. The server begins validating the session identifier and retrieving session data immediately upon receiving the page request, while simultaneously proceeding with content determination. This overlapping of operations maintains data consistency through proper synchronization while significantly improving processing efficiency.
Data Source
AI summary
Techniques are described for determining non-session-related content of a web page through operations that are performed at least partly concurrently with operations for determining session-related content for the page. Session data may be stored on, or accessed through, a centralized session data service that is in communication with a plurality of content servers configured to serve web pages. To mitigate latency incurred through network communications between the content server(s) and the session data service, the generation or retrieval of non-session-related content may begin after the receipt of a page request in a session, and may proceed at least partly in parallel with operations to validate the session identifier, retrieve session data associated with the session identifier, or determine session-related content for the page based on the session data.