Eo-Hyung Lee
Current Organizations / Institutes
The organizations/institutes from the scholar's latest article
Research Subjects
Eo-Hyung Lee has a total of 5 co-authors. Here are the top co-authors by number of shared publications:
- Byeong-Ha Hwang
Department of Cloud, Kakao Enterprise Corp, Seongnam 13494, South Korea
1 shared publication - Choong-Hee Cho
Division of Computer Science and Engineering, Sahmyook University, Hwarangro 815, Seoul 01795, Republic of Korea
1 shared publication - Jung-Bok Lee
Department of Cloud, Kakao Enterprise Corp, Seongnam 13494, South Korea
1 shared publication - Sung-Won Ahn
Department of Cloud, Kakao Enterprise Corp, Seongnam 13494, South Korea
1 shared publication - Tae-Hee Yoo
Department of Cloud, Kakao Enterprise Corporation, Seongnam, South Korea
1 shared publication
Latest Publications
- Open Access
- 30 August 2021
- Published by Institute of Electrical and Electronics Engineers (IEEE) in IEEE Access
- Vol. 9, 123704-123716
High-Performance Software Load Balancer for Cloud-Native Architecture
Driven by increasing in the demand for cloud computing, cloud providers are constantly seeking configuration mechanisms designed to simply install a reliable and easy-to-manage cloud architecture—similar to installing an operating system on a computer using a thumb drive. Accordingly, cloud software components can be packaged into lightweight and portable containers, and then be easily deployed and managed through orchestration tools such as Kubernetes. Similarly, load balancers can also be deployed in containerized cloud environments and managed as a container, simplifying the process of scaling in or out according to the network status or amounts of incoming traffic. In this study, we implemented a containerized high-performance load balancer that distributes traffic using eBPF/XDP within the Linux kernel, which can easily be managed via Kubernetes. We compared the performance of the proposed load balancer with iptables DNAT and loopback based on the RFC2544 performance standard, and also performed tests simulating real-world traffic patterns by using IMIX traffic streams. Our experimental results indicate that the throughput performance of the proposed load balancer is considerably better than that of iptables DNAT; the difference in performance increased with decreasing packet size. The difference in performance between the loopback (representing the theoretical maximum performance limit) and the proposed load balancer was minimal.
- 30 August 2021
- Published by Institute of Electrical and Electronics Engineers (IEEE) in IEEE Access
- Vol. 9, 123704-123716
Open AccessHigh-Performance Software Load Balancer for Cloud-Native Architecture
Driven by increasing in the demand for cloud computing, cloud providers are constantly seeking configuration mechanisms designed to simply install a reliable and easy-to-manage cloud architecture—similar to installing an operating system on a computer using a thumb drive. Accordingly, cloud software components can be packaged into lightweight and portable containers, and then be easily deployed and managed through orchestration tools such as Kubernetes. Similarly, load balancers can also be deployed in containerized cloud environments and managed as a container, simplifying the process of scaling in or out according to the network status or amounts of incoming traffic. In this study, we implemented a containerized high-performance load balancer that distributes traffic using eBPF/XDP within the Linux kernel, which can easily be managed via Kubernetes. We compared the performance of the proposed load balancer with iptables DNAT and loopback based on the RFC2544 performance standard, and also performed tests simulating real-world traffic patterns by using IMIX traffic streams. Our experimental results indicate that the throughput performance of the proposed load balancer is considerably better than that of iptables DNAT; the difference in performance increased with decreasing packet size. The difference in performance between the loopback (representing the theoretical maximum performance limit) and the proposed load balancer was minimal.