Network Interface Device Offloading FaaS Image Construction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The startup duration of Function as a Service (FaaS) applications can impact their time-to-completion and service level agreement (SLA) due to the time-consuming process of constructing execution environments, particularly in scenarios where host resources are heavily utilized for image construction and management.
Innovation Solution
Constructing FaaS images at a network interface device instead of or in addition to the host, which accelerates startup by performing image acquisition, decompression, and caching, reducing CPU utilization and enabling efficient sharing of resources.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If the host constructs FaaS images and manages execution environments, then the startup duration of FaaS applications is reduced, but the CPU utilization and resource consumption of the host increase
Solution Approach 1:
The patent extracts the image construction and caching functions from the host system and relocates them to the network interface device. This separation allows the host to focus on executing FaaS applications while the network interface device handles image acquisition, decompression, and caching, thereby reducing host CPU utilization during application startup.
Solution Approach 2:
The network interface device performs image acquisition, decompression, and caching in advance before the FaaS application needs to start. By preparing the execution environment images beforehand and caching them locally, the system reduces the time required for application startup without requiring the host to expend CPU resources during the critical startup phase.
2Loss of time
If the host caches images in memory to accelerate FaaS application startup, then startup time is reduced, but information security risks and CPU resource consumption increase
Solution Approach 1:
The patent removes the image caching function from the host's memory system and relocates it to the network interface device's local storage. This extraction eliminates the security vulnerability of caching sensitive FaaS images in the host's memory, as the network interface device provides isolated storage that prevents information leakage to unauthorized processes on the host.
Solution Approach 2:
The network interface device acts as an intermediary between the external image repository and the FaaS application execution environment. It handles image acquisition, validation, and caching in an isolated manner, serving as a security buffer that prevents direct access to sensitive images by host processes while still enabling fast startup through local caching.
3Adaptability or versatility
If the host constructs FaaS images, then image construction functionality is provided, but device complexity and resource management overhead increase
Solution Approach 1:
The patent extracts the complex image construction functionality from the host system and assigns it to the network interface device. This includes image acquisition from repositories, decompression of compressed image formats, and caching management. By moving these functions to a dedicated device, the host system's complexity is reduced while retaining full image construction capability through the network interface device.
Solution Approach 2:
The network interface device is enhanced with multi-functionality to perform not only network communication but also image construction, decompression, and caching operations. This universal device approach consolidates multiple functions into a single component, reducing the overall system complexity on the host side while maintaining adaptability for different FaaS application requirements.
Data Source
AI summary
Examples described herein relate to a network interface device that includes circuitry and a memory. In some examples, the circuitry is to perform image construction operations, wherein the image construction operations comprise access to a base image of an application from the memory in the network interface device. In some examples, the circuitry is to provide a host server access to a constructed image bundle of the application.