FRINK Linked Data Fragments server

Matches in SemOpenAlex for { <https://semopenalex.org/work/W2409165084> ?p ?o ?g. }

• W2409165084 abstract "Containers are a convenient way of encapsulating and isolating applications. They incur less overhead than virtual machines and provide more flexibility and versatility to improve server utilization. Many new cloud applications are being written in the microservices style to take advantage of container technologies. Each component of the application can be encapsulated in a separate container, which enables the use of other features such as auto-scaling. However, legacy applications can also benefit from containers which provide more efficient development and deployment models.In modern data centers, orchestration middle-ware is responsible for container placement, SLA enforcement and resource management. The orchestration software can implement various policies for managing the resources. The orchestration software can take corrective actions when detecting inefficiencies in the data center operation to satisfy the current policy.Power efficiency is becoming one of the most important characteristics taken into account when designing a data center and defining policy for the orchestration middleware [4]. Different server architectures have different power efficiency and energy proportionality characteristics. Recent research has shown that heterogeneous systems have the potential to significantly improve energy efficiency[3, 5].Our work focuses on the mechanism required by the middle-ware to implement a power optimization policy. We research migration of containerized applications between servers inside a heterogeneous data center, for the purpose of optimizing power efficiency. Migrating a running container between different architectures relies on the compatibility of the application environment on the source and destination servers. Containers are viewed as a set of one or more processes and each process must have the ability to be migrated. A modified compiler is used to build executables in a manner allowing the program migration between different architectures. The source and destination servers must also have a shared file system and comparable networking capabilities. We take advantage of the recently added user-space page fault feature in the Linux kernel [2] to implement post-copy container migration in CRIU [1]. Post-copy migration significantly reduces perceived down-time of the container, and can potentially reduce network traffic as well.We propose creating a cluster of servers with different architectures (i.e., ARM, POWER, and x86) connected with a high-speed, low-latency network. This cluster will run SaaS applications in a containerized environment. The applications will be built using a specialized toolchain that ensures an identical memory layout across all architectures, enabling seamless migration at runtime. The majority of the challenges in cross-ISA migration are related to the toolchain adaptation, and ensuring the compatibility of the runtime environment across various servers in the cluster.The ability to efficiently migrate running containers between servers with different energy proportionality characteristics provides improved power savings during idle periods without compromising SLA commitments." @default.
• W2409165084 created "2016-06-24" @default.
• W2409165084 creator A5035453669 @default.
• W2409165084 creator A5061913760 @default.
• W2409165084 date "2016-06-06" @default.
• W2409165084 modified "2023-09-24" @default.
• W2409165084 title "Cross-ISA Container Migration" @default.
• W2409165084 cites W2109360947 @default.
• W2409165084 doi "https://doi.org/10.1145/2928275.2933275" @default.
• W2409165084 hasPublicationYear "2016" @default.
• W2409165084 type Work @default.
• W2409165084 sameAs 2409165084 @default.
• W2409165084 citedByCount "9" @default.
• W2409165084 countsByYear W24091650842017 @default.
• W2409165084 countsByYear W24091650842019 @default.
• W2409165084 countsByYear W24091650842020 @default.
• W2409165084 countsByYear W24091650842021 @default.
• W2409165084 crossrefType "proceedings-article" @default.
• W2409165084 hasAuthorship W2409165084A5035453669 @default.
• W2409165084 hasAuthorship W2409165084A5061913760 @default.
• W2409165084 hasConcept C127413603 @default.
• W2409165084 hasConcept C2781018962 @default.
• W2409165084 hasConcept C41008148 @default.
• W2409165084 hasConcept C78519656 @default.
• W2409165084 hasConceptScore W2409165084C127413603 @default.
• W2409165084 hasConceptScore W2409165084C2781018962 @default.
• W2409165084 hasConceptScore W2409165084C41008148 @default.
• W2409165084 hasConceptScore W2409165084C78519656 @default.
• W2409165084 hasLocation W24091650841 @default.
• W2409165084 hasOpenAccess W2409165084 @default.
• W2409165084 hasPrimaryLocation W24091650841 @default.
• W2409165084 hasRelatedWork W1548864292 @default.
• W2409165084 hasRelatedWork W2087770741 @default.
• W2409165084 hasRelatedWork W2356466110 @default.
• W2409165084 hasRelatedWork W2748952813 @default.
• W2409165084 hasRelatedWork W2788712478 @default.
• W2409165084 hasRelatedWork W3016319920 @default.
• W2409165084 hasRelatedWork W3034173033 @default.
• W2409165084 hasRelatedWork W3123056629 @default.
• W2409165084 hasRelatedWork W3158228679 @default.
• W2409165084 hasRelatedWork W4214932653 @default.
• W2409165084 isParatext "false" @default.
• W2409165084 isRetracted "false" @default.
• W2409165084 magId "2409165084" @default.
• W2409165084 workType "article" @default.