The Cost of Virtualizing Time in Linux Containers

Containerization has enabled applications to be deployed in ever-changing environments, restarted, updated, migrated, and frequently rolled back to earlier versions. Because host placement and scheduling are not guaranteed, an application may be restarted in a different host or at a later time, losing its sense of time and refusing service owing to incongruent states or network timeouts. Until now, process time was determined by the host. The most recent Linux time namespace allows for per-service timelines, regardless of the host. Because container engines do not yet support the time namespace, we offer a workflow for creating time-aware containers, as well as the first performance analysis of virtualizing time in Linux containers using this namespace. We consider 11 time-related system calls and their vDSO variants, making this one of the most comprehensive studies on the overhead of time virtualization in the literature. Our findings show that time virtualization adds 2-4% overhead, in line with current containerization overhead.

Automated summary

Containerization technology allows applications to operate in dynamic environments and be time-aware. Although time namespace is not supported by container engines, it is possible to create time-aware containers through a specific workflow, and the performance overhead of time virtualization in containers has been analyzed.