Eo-Hyung Lee

Eo-Hyung Lee

Auto-generated profile, based on publicly available information

Eo-Hyung Lee

Department of Cloud, Kakao Enterprise Corp, Seongnam 13494, South Korea

Research Focus & Metrics

Academic Career Length

6Years (2021-Present)

(Calculated once Scilit publication data is synced: current year − year of first publication + 1)

Representative Publications

View All Publications
30 August 2021 in IEEE Access
Verified
Journal Article
Open access
JLJung-Bok Lee
Jung-Bok Lee
TYTae-Hee Yoo
Tae-Hee Yoo
ELEo-Hyung Lee
Eo-Hyung Lee
BHByeong-Ha Hwang
Byeong-Ha Hwang
SASung-Won Ahn
Sung-Won Ahn
CCChoong-Hee Cho Cho
Choong-Hee Cho Cho
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.