Technologies to allocate resources to start-up a function
Examples described herein relate to launching a function instance based on data related to a previously launched instance of the function and prior to receipt of a portion of the data. In some examples, the memory snapshot is taken during launch of the previously launched instance of the function. In some examples, the first code segments are loaded into memory of a runtime environment during the launch of the previously launched instance of the function in a life cycle execution of the previously launched instance of the function.
1 . At least one non-transitory computer-readable medium comprising instructions stored thereon, that if executed by one or more processors, cause the one or more processors to:
launch a function instance by:
retrieving data related to a previously launched instance of the function, wherein the data comprises a memory snapshot taken during launch of the previously launched instance of the function and the data comprises first code segments loaded into a runtime environment during a launch of the previously launched instance of the function,
after retrieval of copies of the first code segments, retrieve second code segments associated with the function instance and access the retrieved first code segments and retrieved second code segments, and
while retrieving the second code segments, execute a function handler to launch the function instance based on the memory snapshot and the first code segments and retrieved code segments of the second code segments, wherein:
the memory snapshot comprises memory content of the previously launched instance of the function after completion of creating a sandbox but before initiation of a function handler for the previously launched instance of the function,
the first and second code segments are different parts of the function instance.
2 . The computer-readable medium of claim 1 , wherein the launching the function instance based on data related to the previously launched instance of the function and prior to receipt of a portion of the data comprises:
at least partially in parallel:
clone the memory snapshot, and
receive the first code segments into a memory device.
3 . The computer-readable medium of claim 1 , wherein the memory snapshot was captured after completion of creating the previously launched instance of the function's running environment and loading and initializing a language runtime of the previously launched instance of the function.
4 . The computer-readable medium of claim 1 , comprising instructions stored thereon, that if executed by one or more processors, cause the one or more processors to:
launch the function instance by executing a function handler based on availability of the memory snapshot and the first code segments.
5 . The computer-readable medium of claim 1 , wherein the launch the function instance based on the data related to the previously launched instance of the function and prior to receipt of a portion of the data comprises:
associate the launched function instance with one or more unique identifiers (IDs).
6 . The computer-readable medium of claim 1 , wherein the launched function instance comprises a micro virtual machine.
7 . The computer-readable medium of claim 1 , comprising instructions stored thereon, that if executed by one or more processors, cause the one or more processors to:
delete the function instance after completion of execution of the function instance.
8 . An apparatus comprising:
at least one processor;
at least one memory comprising instructions stored thereon, that if executed by the at least one processor, cause the at least one processor to:
launch a function instance by:
retrieval of data related to a previously launched instance of the function, wherein the data comprises a memory snapshot taken during launch of the previously launched instance of the function and the data comprises first code segments loaded into a runtime environment during a launch of the previously launched instance of the function,
after retrieval of copies of the first code segments, retrieve second code segments associated with the function instance and access the retrieved first code segments and retrieved second code segments, and
during retrieval the second code segments, execute a function handler to launch the function instance based on the memory snapshot and the first code segments and retrieved code segments of the second code segments, wherein:
the memory snapshot comprises memory content of the previously launched instance of the function after completion of creating a sandbox but before initiation of a function handler for the previously launched instance of the function,
the first and second code segments are different parts of the function instance.
9 . The apparatus of claim 8 , wherein the launch of the function instance based on data related to the previously launched instance of the function and prior to receipt of a portion of the data comprises:
at least partially in parallel:
clone the memory snapshot, and
receive the first code segments into a memory device.
10 . The apparatus of claim 8 , wherein the memory snapshot was captured after completion of creating of the previously launched instance of the function's running environment and loading and initializing a language runtime of the previously launched instance of the function.
11 . The apparatus of claim 8 , wherein the at least one memory comprises instructions stored thereon, that if executed by the at least one processor, cause the at least one processor to:
launch the function by execution of a function handler based on availability of the memory snapshot and the first code segments.
12 . The apparatus of claim 8 , wherein to launch the function instance based on data related to the previously launched instance of the function and prior to receipt of a portion of the data, the at least one processor is to:
associate the launched function instance with one or more unique identifiers (IDs).
13 . The apparatus of claim 8 , comprising a server, wherein the server comprises the at least one processor, the at least one memory, and a network interface device and wherein the network interface device is to receive the data and store the data into the at least one memory.
14 . The apparatus of claim 13 , comprising a datacenter, wherein the datacenter comprises a second server, wherein the second server is to store the data.
15 . A method comprising:
launch a function instance by:
retrieving data related to a previously launched instance of the function, wherein the data comprises a memory snapshot taken during launch of the previously launched instance of the function and the data comprises first code segments loaded into a runtime environment during a launch of the previously launched instance of the function,
after retrieval of copies of the first code segments, retrieving second code segments associated with the function instance and accessing the retrieved first code segments and retrieved second code segments, and
during retrieval the second code segments, execute a function handler to launch the function instance based on the memory snapshot and the first code segments and retrieved code segments of the second code segments, wherein:
the memory snapshot comprises memory content of the previously launched instance of the function after completion of creating a sandbox but before initiation of a function handler for the previously launched instance of the function,
the first and second code segments are different parts of the function instance.
16 . The method of claim 15 , wherein the launching the function instance based on data related to the previously launched instance of the function and prior to receipt of a portion of the data comprises:
at least partially in parallel:
cloning the memory snapshot, and
receiving the first code segments into memory.