Application-Tailored Display Object Pre-Inflation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Content-intensive applications face significant latency issues due to the creation and inflation of display objects, particularly in scenarios with variable and lengthy content sections, where request-driven real-time inflation is insufficient.
Innovation Solution
Implementing application-specific policies to pre-inflate only the most costly display objects and elements before they are requested, storing them in a recycler for later retrieval and reuse, which includes nested display objects.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If display objects are created and inflated in real-time when requested, then memory usage is optimized, but latency increases significantly
Solution Approach 1:
The system performs preliminary action by pre-inflating display objects before they are actually requested or needed. The recycler pre-inflates display objects as they are created, storing them in an inflated state ready for immediate use. This eliminates the latency of real-time inflation while managing memory through selective pre-inflation of objects that are likely to be needed soon.
2Loss of time
If all display objects are pre-inflated, then latency is reduced, but memory usage increases significantly
Solution Approach 1:
The system applies local quality by making different parts of the system have different properties. The recycler selectively pre-inflates only certain display objects based on specific criteria (such as likelihood of being needed, complexity of inflation, etc.), rather than uniformly pre-inflating all objects. This localized approach reduces memory usage while still providing latency benefits for the most critical objects.
Solution Approach 2:
The system changes parameters by adjusting which display objects are pre-inflated based on varying conditions. The recycler uses policies that can change parameters such as the threshold for pre-inflation, the types of objects to pre-inflate, and the recycler size limits. This allows dynamic adjustment of memory usage versus latency trade-offs based on available resources and application needs.
3Productivity
If request-driven real-time inflation is used, then memory efficiency is maintained, but rendering performance becomes insufficient
Solution Approach 1:
The recycler performs preliminary action by pre-inflating display objects and storing them ready for immediate retrieval. When a display object is needed for rendering, the system can retrieve it from the recycler in its already-inflated state, significantly improving rendering performance. The preliminary inflation is managed through policies that balance memory usage with rendering performance requirements.
Data Source
AI summary
In one embodiment, a computing device receives a request for content in a first portion of a content layout in a displayable region of a screen associated with the computing device. The device may pre-inflate at least one selected element of a display object for a second portion of the content layout, and then store the element in an application-tailored recycler. Selection of the at least one selected element may be based on dimensions of the displayable region, available memory of the computing device, or application-specific rules. The device may then retrieve, in response to a request for content in the second portion of the content layout, the element from the application-tailored recycler, update other elements of the display object as needed for the second portion of the content layout, and return the display object.