디스크 입출력 및 네트워크 최적화

Kafka is a high-throughput, low-latency system. Its performance heavily depends on the underlying infrastructure: disk I/O and network bandwidth.

Optimizing these components is crucial for handling large volumes of data efficiently, ensuring your Kafka cluster can keep up with demand.

Kafka brokers store all messages on disk in immutable, ordered log files. This design ensures durability and allows consumers to read data at their own pace.

Kafka primarily performs sequential writes to these log files. Sequential I/O is much faster than random I/O, even on traditional Hard Disk Drives (HDDs).

While Kafka's sequential writes make HDDs viable, Solid State Drives (SSDs) generally offer superior performance, especially for operations like log compaction or recovery.

• SSDs: Higher IOPS, lower latency, better for mixed workloads or when random access occurs (e.g., during recovery).
• HDDs: Cost-effective for pure sequential writes, but can be a bottleneck for random reads/writes.

For production, SSDs are often recommended for their consistent performance.

RAID (Redundant Array of Independent Disks) configurations can enhance both performance and fault tolerance.

• RAID 0 (Striping): Spreads data across multiple disks, significantly boosting read/write speeds. However, it offers no redundancy; if one disk fails, all data is lost.
• RAID 10 (Striping + Mirroring): Combines RAID 0's speed with RAID 1's mirroring for redundancy. It's often the recommended choice for Kafka, providing both high performance and data protection.

The filesystem choice and its configuration can impact Kafka's disk performance.

• XFS: Often recommended for Kafka due to its robust performance with large files and excellent scalability.
• Ext4: A common and reliable choice, but XFS can sometimes offer better throughput for Kafka's specific I/O patterns.

Ensure your filesystem is mounted with appropriate options, like noatime, to reduce unnecessary disk writes.

The operating system's disk scheduler manages the order in which I/O requests are sent to the disk. Different schedulers optimize for different workloads:

• noop: A simple FIFO queue, often best for SSDs or virtualized environments where the hypervisor handles scheduling.
• deadline: Prioritizes I/O requests to prevent starvation, good for mixed workloads.
• CFQ (Completely Fair Queuing): Attempts to fairly distribute I/O bandwidth among processes, but can introduce latency.

For Kafka on SSDs, noop is generally a good starting point.

Kafka's ability to handle high data throughput depends heavily on your network infrastructure. Producers send data, consumers receive it, and brokers replicate it – all over the network.

Using 10 Gigabit Ethernet (10GbE) or higher for your Kafka brokers is a common recommendation to prevent network bottlenecks. Ensure your network switches and cabling also support these speeds.

TCP buffers at both the operating system and Kafka levels can significantly affect network performance.

• OS-level: Tune net.core.wmem_default, net.core.rmem_default, and related settings to allow larger buffers.
• Kafka-level: Adjust socket.send.buffer.bytes (default 100KB) and socket.receive.buffer.bytes (default 100KB) in your broker configuration to match your network capacity. Larger buffers can improve throughput for high-latency networks.

Modern Network Interface Cards (NICs) often have hardware offloading features that can reduce CPU utilization and improve network throughput.

• Checksum Offloading: NIC calculates/verifies TCP/IP checksums.
• TSO (TCP Segmentation Offload) & GSO (Generic Segmentation Offload): NIC handles segmenting large packets, reducing CPU overhead.

Ensure these features are enabled on your Kafka broker servers for optimal network performance. You can often check/configure them using tools like ethtool.

Time to test your understanding of Kafka infrastructure optimization!

Great job! In this lesson, we explored how to optimize the underlying infrastructure for Kafka.

• We discussed the importance of SSDs and RAID 10 for disk I/O.
• We learned about recommended filesystems like XFS and OS disk schedulers.
• We covered boosting network performance with high-speed NICs, TCP buffer tuning, and hardware offloading.

By carefully configuring these foundational elements, you can unlock significant performance gains for your Kafka cluster!