基于容器编排工具比较的自动化资源管理系统

Pub Date : 2023-01-01 DOI:10.12720/jait.14.3.501-509
B. Purahong, J. Sithiyopasakul, P. Sithiyopasakul, A. Lasakul, C. Benjangkaprasert
{"title":"基于容器编排工具比较的自动化资源管理系统","authors":"B. Purahong, J. Sithiyopasakul, P. Sithiyopasakul, A. Lasakul, C. Benjangkaprasert","doi":"10.12720/jait.14.3.501-509","DOIUrl":null,"url":null,"abstract":"—The goal of this article is to study and analyze the container orchestration technology Kubernetes, Docker Swarm, and Apache Mesos by performing performance evaluations and inspecting how many requests and responses the server can handle. Due to the fact that managing information system resources is a challenge in terms of performance, usability, reliability, and the cost of information resources. Some orchestration tools cannot automatically allocate resources depending on the scope of the information system resource management. This leads to allocating resources more than the needs of system requirements, resulting in excessive costs. Therefore, this article proposed testing the system by measuring its effectiveness using a structured process by examining measurement variables such as the number of requests per second, number of responses to requests, and resource extension period using all three-orchestration technology. From the testing and analysis of all three variables as mentioned, it is possible to know the efficiency of the Kubernetes technology in such a similar environment and compared it with other orchestration tools like Docker Swarm and Apache Mesos orchestrator. For Kubernetes, Docker Swarm, and Apache Mesos, the mean value of its handling average request per minute is 30,677.25/min, 33,688.67/min, and 29,682.6/min, respectively. Swarm performed better in aspects of handling requests per minute by 9.35% of the difference when compared to Kubernetes and by 12.64% when compared to Apache Mesos. However, there are several things which should be taken into consideration because each orchestration tool has its own strong and weak points. The testing experiment could display a piece of information on the dashboard for visualization and analytic purposes and there is an elaboration at the end of when to use which container orchestration tool to suit the business proposes the most .","PeriodicalId":0,"journal":{"name":"","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"2023-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":"{\"title\":\"Automated Resource Management System Based upon Container Orchestration Tools Comparison\",\"authors\":\"B. Purahong, J. Sithiyopasakul, P. Sithiyopasakul, A. Lasakul, C. Benjangkaprasert\",\"doi\":\"10.12720/jait.14.3.501-509\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"—The goal of this article is to study and analyze the container orchestration technology Kubernetes, Docker Swarm, and Apache Mesos by performing performance evaluations and inspecting how many requests and responses the server can handle. Due to the fact that managing information system resources is a challenge in terms of performance, usability, reliability, and the cost of information resources. Some orchestration tools cannot automatically allocate resources depending on the scope of the information system resource management. This leads to allocating resources more than the needs of system requirements, resulting in excessive costs. Therefore, this article proposed testing the system by measuring its effectiveness using a structured process by examining measurement variables such as the number of requests per second, number of responses to requests, and resource extension period using all three-orchestration technology. From the testing and analysis of all three variables as mentioned, it is possible to know the efficiency of the Kubernetes technology in such a similar environment and compared it with other orchestration tools like Docker Swarm and Apache Mesos orchestrator. For Kubernetes, Docker Swarm, and Apache Mesos, the mean value of its handling average request per minute is 30,677.25/min, 33,688.67/min, and 29,682.6/min, respectively. Swarm performed better in aspects of handling requests per minute by 9.35% of the difference when compared to Kubernetes and by 12.64% when compared to Apache Mesos. However, there are several things which should be taken into consideration because each orchestration tool has its own strong and weak points. The testing experiment could display a piece of information on the dashboard for visualization and analytic purposes and there is an elaboration at the end of when to use which container orchestration tool to suit the business proposes the most .\",\"PeriodicalId\":0,\"journal\":{\"name\":\"\",\"volume\":null,\"pages\":null},\"PeriodicalIF\":0.0,\"publicationDate\":\"2023-01-01\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"0\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.12720/jait.14.3.501-509\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.12720/jait.14.3.501-509","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 0

摘要

本文的目标是通过执行性能评估和检查服务器可以处理多少请求和响应来研究和分析容器编排技术Kubernetes, Docker Swarm和Apache Mesos。由于管理信息系统资源在性能、可用性、可靠性和信息资源成本方面是一个挑战。某些编排工具不能根据信息系统资源管理的范围自动分配资源。这将导致分配的资源超过系统需求的需要,从而导致成本过高。因此,本文建议使用结构化流程来测试系统的有效性,方法是检查度量变量,例如每秒请求数、请求响应数和使用所有三种编排技术的资源扩展周期。通过对上述三个变量的测试和分析,我们可以了解Kubernetes技术在类似环境中的效率,并将其与其他编排工具(如Docker Swarm和Apache Mesos orchestrator)进行比较。对于Kubernetes, Docker Swarm和Apache Mesos,其平均每分钟处理请求的平均值分别为30,677.25/min, 33,688.67/min和29,682.6/min。与Kubernetes相比,Swarm在每分钟处理请求方面表现更好,差异为9.35%,与Apache Mesos相比,差异为12.64%。然而,由于每个编排工具都有自己的优缺点,因此有几件事情需要考虑。测试实验可以在仪表板上显示一条信息,用于可视化和分析目的,并且在最后详细说明何时使用哪个容器编排工具最适合业务建议。
本文章由计算机程序翻译,如有差异,请以英文原文为准。
分享
查看原文
Automated Resource Management System Based upon Container Orchestration Tools Comparison
—The goal of this article is to study and analyze the container orchestration technology Kubernetes, Docker Swarm, and Apache Mesos by performing performance evaluations and inspecting how many requests and responses the server can handle. Due to the fact that managing information system resources is a challenge in terms of performance, usability, reliability, and the cost of information resources. Some orchestration tools cannot automatically allocate resources depending on the scope of the information system resource management. This leads to allocating resources more than the needs of system requirements, resulting in excessive costs. Therefore, this article proposed testing the system by measuring its effectiveness using a structured process by examining measurement variables such as the number of requests per second, number of responses to requests, and resource extension period using all three-orchestration technology. From the testing and analysis of all three variables as mentioned, it is possible to know the efficiency of the Kubernetes technology in such a similar environment and compared it with other orchestration tools like Docker Swarm and Apache Mesos orchestrator. For Kubernetes, Docker Swarm, and Apache Mesos, the mean value of its handling average request per minute is 30,677.25/min, 33,688.67/min, and 29,682.6/min, respectively. Swarm performed better in aspects of handling requests per minute by 9.35% of the difference when compared to Kubernetes and by 12.64% when compared to Apache Mesos. However, there are several things which should be taken into consideration because each orchestration tool has its own strong and weak points. The testing experiment could display a piece of information on the dashboard for visualization and analytic purposes and there is an elaboration at the end of when to use which container orchestration tool to suit the business proposes the most .
求助全文
通过发布文献求助,成功后即可免费获取论文全文。 去求助
×
引用
GB/T 7714-2015
复制
MLA
复制
APA
复制
导出至
BibTeX EndNote RefMan NoteFirst NoteExpress
×
提示
您的信息不完整,为了账户安全,请先补充。
现在去补充
×
提示
您因"违规操作"
具体请查看互助需知
我知道了
×
提示
确定
请完成安全验证×
copy
已复制链接
快去分享给好友吧!
我知道了
右上角分享
点击右上角分享
0
联系我们:info@booksci.cn Book学术提供免费学术资源搜索服务,方便国内外学者检索中英文文献。致力于提供最便捷和优质的服务体验。 Copyright © 2023 布克学术 All rights reserved.
京ICP备2023020795号-1
ghs 京公网安备 11010802042870号
Book学术文献互助
Book学术文献互助群
群 号:481959085
Book学术官方微信