Asynchronous Page Rendering via CDN Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current page loading technologies face inefficiencies due to thread pool limitations, leading to blocked rendering tasks and poor user experience when handling high volumes of page access requests, resulting in delayed loading times and timeouts.
Innovation Solution
Implementing asynchronous rendering of page frameworks and modules, where the Content Delivery Network receives requests, determines cache availability, and distributes rendering tasks between servers and Redis caching, allowing for faster page assembly and delivery to browsers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If the application server uses a thread pool to render pages, then the rendering capability is maintained at a manageable level, but when the number of page access requests exceeds the maximum thread pool capacity, rendering tasks are blocked and page loading times out
Solution Approach 1:
The patent divides the page rendering process into two independent segments: page framework rendering and page module rendering. The page framework is rendered once and cached, while page modules are rendered on-demand when needed. This segmentation allows the system to handle more concurrent requests without requiring a proportionally larger thread pool, as multiple requests can share the same framework rendering resources.
Solution Approach 2:
The patent implements preliminary rendering of the page framework before actual page module requests are processed. By pre-rendering and caching the framework, the system prepares common resources in advance, reducing the burden on the thread pool during actual page loading operations and preventing rendering task blocks.
2Reliability
If the entire page is rendered dynamically by the application server, then the page content is fresh and up-to-date, but the page loading time increases and the page loading rate decreases
Solution Approach 1:
The patent segments the page into a reusable framework and interchangeable modules. The framework contains common structures and styles that can be pre-rendered and cached, while only the specific modules needed for each request are rendered dynamically. This reduces the overall rendering time while maintaining content freshness through on-demand module loading.
Solution Approach 2:
The page framework is pre-rendered and cached before actual page requests are processed. This preliminary action provides a foundation of fresh, up-to-date content structure that can be quickly assembled with required modules, reducing the time needed for complete page rendering while ensuring content freshness.
3Productivity
If the page is cached on the hard disk of the Web server, then the page loading rate increases, but the storage requirements and cache management complexity increase
Solution Approach 1:
The patent segments the caching strategy into two levels: framework-level caching (long-term, high hit rate) and module-level caching (short-term, on-demand). This segmentation allows the system to cache only the most valuable content (framework) while maintaining flexibility to load specific modules when needed, reducing overall storage requirements and cache management complexity compared to caching entire pages.
Data Source
AI summary
A method and system for increasing a page loading rate, the method comprising: a Content Delivery Network receiving a page framework request sent by a browser, and launching a page framework request to a server; the server rendering a page framework on the basis of the page framework request, and sending the page framework to the browser by the Content Delivery Network; the browser parsing the page framework to obtain a page module identifier, and launching a page module request including the page module identifier to the server by the Content Delivery Network; the server rendering a page module on the basis of the page framework module request, and sending the page module to the Content Delivery Network; and the Content Delivery Network populating the page module into the page framework to form a page on the basis of the page module identifier, and sending the page to the browser.