The original paper is in English. Non-English content has been machine-translated and may contain typographical errors or mistranslations. ex. Some numerals are expressed as "XNUMX".
Copyrights notice
The original paper is in English. Non-English content has been machine-translated and may contain typographical errors or mistranslations. Copyrights notice
컨테이너는 가상 머신에 비해 가벼운 대안을 제공하며 클라우드에서의 애플리케이션 통합을 위해 선호되는 선택이 되었습니다. 그러나 커널 구성 요소를 공유하면 컨테이너의 I/O 성능 및 격리가 위반될 수 있습니다. 파일 시스템 저널링은 특히 데이터베이스 관리 시스템(DBMS)을 통합할 때 컨테이너에서 심각한 성능 부작용을 가져온다는 사실이 널리 알려져 있습니다. 컨테이너 간에 저널링 모듈을 공유하면 컨테이너 간에 성능 종속성이 발생합니다. 이러한 종속성은 리소스 컨트롤러에 의해 적용되는 리소스 소비를 위반하고 저널링 모듈의 경합으로 인해 I/O 성능을 저하시킵니다. 운영 체제 개발자들은 저널링 문제를 해결하기 위해 파일 시스템의 새로운 디자인이나 새로운 저널링 메커니즘을 연구해 왔습니다. 본 논문에서는 파일 시스템을 재설계하거나 새로운 저널링 방법을 구현하지 않고도 저널링 문제를 극복할 수 있음을 보여줍니다. 기존 파일 시스템의 컨테이너를 주의 깊게 구성하면 문제를 원활하게 해결할 수 있습니다. 우리가 권장하는 구성은 1) 각 컨테이너에 가상 블록 장치를 제공하여 자체 저널링 모듈을 갖는 컨테이너별 저널링과 2) 각 컨테이너에 대해 별도로 저널링 I/O를 계산하는 것으로 구성됩니다. 실험 결과에 따르면 우리의 구성은 저널링 관련 문제를 해결하고 MySQL 성능을 3.4배 향상시키며 컨테이너 간에 합리적인 성능 격리를 달성하는 것으로 나타났습니다.
Asraa ABDULRAZAK ALI MARDAN
Keio University
Kenji KONO
Keio University
가상화, 컨테이너, DBMS, 저널링 파일 시스템
The copyright of the original papers published on this site belongs to IEICE. Unauthorized use of the original or translated papers is prohibited. See IEICE Provisions on Copyright for details.
부
Asraa ABDULRAZAK ALI MARDAN, Kenji KONO, "Alleviating File System Journaling Problem in Containers for DBMS Consolidation" in IEICE TRANSACTIONS on Information,
vol. E104-D, no. 7, pp. 931-940, July 2021, doi: 10.1587/transinf.2020EDP7178.
Abstract: Containers offer a lightweight alternative over virtual machines and become a preferable choice for application consolidation in the clouds. However, the sharing of kernel components can violate the I/O performance and isolation in containers. It is widely recognized that file system journaling has terrible performance side effects in containers, especially when consolidating database management systems (DBMSs). The sharing of journaling modules among containers causes performance dependency among them. This dependency violates resource consumption enforced by the resource controller, and degrades I/O performance due to the contention of the journaling module. The operating system developers have been working on novel designs of file systems or new journaling mechanisms to solve the journaling problems. This paper shows that it is possible to overcome journaling problems without re-designing file systems or implementing a new journaling method. A careful configuration of containers in existing file systems can gracefully solve the problems. Our recommended configuration consists of 1) per-container journaling by presenting each container with a virtual block device to have its own journaling module, and 2) accounting journaling I/Os separately for each container. Our experimental results show that our configuration resolves journaling-related problems, improves MySQL performance by 3.4x, and achieves reasonable performance isolation among containers.
URL: https://global.ieice.org/en_transactions/information/10.1587/transinf.2020EDP7178/_p
부
@ARTICLE{e104-d_7_931,
author={Asraa ABDULRAZAK ALI MARDAN, Kenji KONO, },
journal={IEICE TRANSACTIONS on Information},
title={Alleviating File System Journaling Problem in Containers for DBMS Consolidation},
year={2021},
volume={E104-D},
number={7},
pages={931-940},
abstract={Containers offer a lightweight alternative over virtual machines and become a preferable choice for application consolidation in the clouds. However, the sharing of kernel components can violate the I/O performance and isolation in containers. It is widely recognized that file system journaling has terrible performance side effects in containers, especially when consolidating database management systems (DBMSs). The sharing of journaling modules among containers causes performance dependency among them. This dependency violates resource consumption enforced by the resource controller, and degrades I/O performance due to the contention of the journaling module. The operating system developers have been working on novel designs of file systems or new journaling mechanisms to solve the journaling problems. This paper shows that it is possible to overcome journaling problems without re-designing file systems or implementing a new journaling method. A careful configuration of containers in existing file systems can gracefully solve the problems. Our recommended configuration consists of 1) per-container journaling by presenting each container with a virtual block device to have its own journaling module, and 2) accounting journaling I/Os separately for each container. Our experimental results show that our configuration resolves journaling-related problems, improves MySQL performance by 3.4x, and achieves reasonable performance isolation among containers.},
keywords={},
doi={10.1587/transinf.2020EDP7178},
ISSN={1745-1361},
month={July},}
부
TY - JOUR
TI - Alleviating File System Journaling Problem in Containers for DBMS Consolidation
T2 - IEICE TRANSACTIONS on Information
SP - 931
EP - 940
AU - Asraa ABDULRAZAK ALI MARDAN
AU - Kenji KONO
PY - 2021
DO - 10.1587/transinf.2020EDP7178
JO - IEICE TRANSACTIONS on Information
SN - 1745-1361
VL - E104-D
IS - 7
JA - IEICE TRANSACTIONS on Information
Y1 - July 2021
AB - Containers offer a lightweight alternative over virtual machines and become a preferable choice for application consolidation in the clouds. However, the sharing of kernel components can violate the I/O performance and isolation in containers. It is widely recognized that file system journaling has terrible performance side effects in containers, especially when consolidating database management systems (DBMSs). The sharing of journaling modules among containers causes performance dependency among them. This dependency violates resource consumption enforced by the resource controller, and degrades I/O performance due to the contention of the journaling module. The operating system developers have been working on novel designs of file systems or new journaling mechanisms to solve the journaling problems. This paper shows that it is possible to overcome journaling problems without re-designing file systems or implementing a new journaling method. A careful configuration of containers in existing file systems can gracefully solve the problems. Our recommended configuration consists of 1) per-container journaling by presenting each container with a virtual block device to have its own journaling module, and 2) accounting journaling I/Os separately for each container. Our experimental results show that our configuration resolves journaling-related problems, improves MySQL performance by 3.4x, and achieves reasonable performance isolation among containers.
ER -