Customer Page Code Loading in Web Hosting

Solution Overview

Problem

Existing network page generation systems face inefficiencies in loading customer-supplied code, often requiring immediate loading upon submission or with each request, leading to initial performance degradation for users.

Innovation Solution

Implementing a method where customer-supplied page generation code is loaded into memory only in response to the first network page request, allowing for delayed loading and subsequent improved performance on subsequent requests, with the entire web application being loaded concurrently if necessary.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If customer-supplied page generation code is loaded into memory upon initial submission, then subsequent page generation performance is improved, but initial memory usage increases and loading time is wasted

Engineering Contradiction:

Improvepage generation performanceVSAvoidinitial loading time

Core Design Contradiction:

ProductivityVSLoss of time

Solution Approach 1:

The system performs preliminary validation and compilation of customer-supplied page generation code when first submitted, storing the validated code in a cached state. This preliminary action ensures that when the code is subsequently loaded into memory for execution, it can be quickly activated without validation overhead, thus improving page generation performance while minimizing initial loading time.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system dynamically determines when to load customer-supplied code into memory based on actual page generation requests. Rather than statically loading all code upfront, the system maintains a dynamic state where code is loaded only when needed, optimizing the balance between memory usage and performance based on real-time demand patterns.

Inventive Principle:

Principle #15Dynamics

2Reliability

If customer-supplied page generation code is loaded into memory with each network page request, then fresh code is always available, but response time increases due to repeated loading

Engineering Contradiction:

Improvecode freshnessVSAvoidresponse time

Core Design Contradiction:

ReliabilityVSSpeed

Solution Approach 1:

The system performs preliminary validation and compilation of customer-supplied page generation code when first submitted, storing the validated code in a cached state. This preliminary action ensures that when the code is subsequently loaded into memory for execution, it can be quickly activated without validation overhead, thus improving page generation performance while minimizing initial loading time.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

Once customer-supplied code is validated and loaded into memory, the system maintains it in a ready-to-execute state continuously, avoiding repeated loading operations. This continuous availability of pre-validated code ensures both code freshness and fast response times, as the code remains accessible without needing to be reloaded with each request.

Inventive Principle:

Principle #20Continuity of useful action

3Productivity

If the entire web application is loaded into memory responsive to the first network page request, then subsequent requests benefit from cached code, but the first request experiences performance degradation

Engineering Contradiction:

Improvesubsequent request performanceVSAvoidfirst request latency

Core Design Contradiction:

ProductivityVSLoss of time

Solution Approach 1:

The system performs preliminary validation and compilation of customer-supplied page generation code when first submitted, storing the validated code in a cached state. This preliminary action ensures that when the code is subsequently loaded into memory for execution, it can be quickly activated without validation overhead, thus improving page generation performance while minimizing initial loading time.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system pre-allocates and prepares memory resources for the web application during the initial submission phase, cushioning against the performance impact of the first request. By having memory resources ready and code pre-validated, the system minimizes the latency penalty of the first request while ensuring rapid performance for subsequent requests.

Inventive Principle:

Principle #11Beforehand cushioning (Prior cushioning)

Data Source

PatentUS8959426B1Loading customer-supplied network page generation code

Publication Date: 2015.02.17 AMAZON TECH INC

AI summary

Disclosed are various embodiments for loading page generation code supplied by customers into a memory. A request for a network page is obtained from a client. The network page is associated with a network site hosted by a hosting provider on behalf of a customer. It is determined whether page generation code configured to generate at least a portion of the network page is preloaded into a memory. Such page generation code is customer supplied. The page generation code is loaded into the memory in response to the request and in response to determining that the page generation code is not preloaded into the memory. The page generation code is executed to generate the at least a portion of the network page in response to the request.