generation ● SDK generation and licence information and source package extraction ● Reduce image footprint ● Own application integration E.L.B.E. Limitations using Debian & E.L.B.E. ● Only limited number generation ● SDK generation and licence information and source package extraction ● Reduce image footprint ● Own application integration 3) Benefit of a combination ★ Yocto + Debian = ? Yocto + Debian app integration HW-specific SW like kernel / bootloader buildable Use Debian sources Default footprint / reducible? 10MB 300MB / with Yocto methods 300MB / not yet Non-Debian archs buildable use an

ContainerOS Current Implementation Iteration is key ● Move back to eBPF module to reduce our OS footprint ● Smarter rules based on user behavior ● Automatically respond to malicious actions without

event such as a system update. Function Description Snapshot • The snapshot has a smaller footprint as it saves just the differences (partition 3 in Figure 7.1) compared to the out-of-factory rootfs to restore the computer that the snapshot was taken from. Backup • The backup has a larger footprint as it saves the entire system including the out-of-factory rootfs. • The backup can be exported

time. Worker generally is a good choice for high-traffic servers because it has a smaller memory footprint than the prefork MPM. The event MPM is threaded like the Worker MPM, but is designed to allow more memory, but it wouldn't be the safest option for the sake of the server's stability and memory footprint. Background material The event model was made possible by the introduction of new APIs into the chunk itself. When many small chunks are generated by a request, this can create a large memory footprint while the request is being processed, and an unnecessarily large amount of data on the wire. The

time. Worker generally is a good choice for high-traffic servers because it has a smaller memory footprint than the prefork MPM. The event MPM is threaded like the Worker MPM, but is designed to allow more memory, but it wouldn't be the safest option for the sake of the server's stability and memory footprint. Background material The event model was made possible by the introduction of new APIs into the chunk itself. When many small chunks are generated by a request, this can create a large memory footprint while the request is being processed, and an unnecessarily large amount of data on the wire. The

time. Worker generally is a good choice for high-traffic servers because it has a smaller memory footprint than the prefork MPM. The event MPM is threaded like the Worker MPM, but is designed to allow more memory, but it wouldn't be the safest option for the sake of the server's stability and memory footprint. Background material The event model was made possible by the introduction of new APIs into the chunk itself. When many small chunks are generated by a request, this can create a large memory footprint while the request is being processed, and an unnecessarily large amount of data on the wire. The

time. Worker generally is a good choice for high-traffic servers because it has a smaller memory footprint than the prefork MPM. The event MPM is threaded like the Worker MPM, but is designed to allow more memory, but it wouldn't be the safest option for the sake of the server's stability and memory footprint. Background material The event model was made possible by the introduction of new APIs into the chunk itself. When many small chunks are generated by a request, this can create a large memory footprint while the request is being processed, and an unnecessarily large amount of data on the wire. The

time. Worker generally is a good choice for high-traffic servers because it has a smaller memory footprint than the prefork MPM. • The EVENT MPM is threaded like the Worker MPM, but is designed to allow chunk itself. When many small chunks are generated by a request, this can create a large memory footprint while the request is being processed, and an unnecessarily large amount of data on the wire. The always need more memory than HTTP/1.1 processing. There are three directives which steer the memory footprint of a HTTP/2 connection: H2MAXSESSIONSTREAMS, H2WINDOWSIZE and H2STREAMMAXMEMSIZE. H2MAXSESSIONSTREAMS

time. Worker generally is a good choice for high-traffic servers because it has a smaller memory footprint than the prefork MPM. • The EVENT MPM is threaded like the Worker MPM, but is designed to allow chunk itself. When many small chunks are generated by a request, this can create a large memory footprint while the request is being processed, and an unnecessarily large amount of data on the wire. The always need more memory than HTTP/1.1 processing. There are three directives which steer the memory footprint of a HTTP/2 connection: H2MAXSESSIONSTREAMS, H2WINDOWSIZE and H2STREAMMAXMEMSIZE. H2MAXSESSIONSTREAMS

time. Worker generally is a good choice for high-traffic servers because it has a smaller memory footprint than the prefork MPM. The event MPM is threaded like the Worker MPM, but is designed to allow more memory, but it wouldn't be the safest option for the sake of the server's stability and memory footprint. Background material The event model was made possible by the introduction of new APIs into the chunk itself. When many small chunks are generated by a request, this can create a large memory footprint while the request is being processed, and an unnecessarily large amount of data on the wire. The