1 views collected around this technical thread.
This article explains the root causes of Java NIO empty polling, its impact on CPU usage, and presents Netty's multi‑layer detection, threshold‑based auto‑rebuild, and selector reconstruction techniques, along with configuration tips and future optimization directions for high‑concurrency backend systems.
Learn five Java file copy techniques—from basic streams to NIO Files.copy, FileChannel, and RandomAccessFile—detailing their implementations, performance differences, and ideal use cases for small, large, and massive files, helping you choose the most efficient method for your project.
The presentation by NIO senior technology planning expert Chen Jiong explores the development trends of intelligent electric vehicles, showcases how large AI models empower various automotive scenarios, and shares NIO's practical implementations, offering insights on industry-focused solutions, problem‑driven application, and unified architecture design.
The article chronicles the Rainbow Bridge proxy’s shift from a blocking BIO JDBC driver to a custom Netty‑based NIO driver with an event‑loop‑affine connection pool, detailing optimizations such as codec skipping and lock‑free queues that yield up to 67% higher throughput, 37% lower load, and a 98% reduction in thread usage.
This article explains the evolution of I/O multiplexing in Java, covering the birth of multiplexing, the introduction of NIO with Selector, and detailed comparisons of select, poll, and epoll mechanisms, including their APIs, internal workings, and performance considerations for high‑concurrency network programming.
This article provides a comprehensive overview of Java I/O models—including blocking (BIO), non‑blocking (NIO), asynchronous (AIO)—explains their differences, demonstrates file and network programming with code examples, and introduces Netty as a high‑performance framework for building scalable server applications.
This article presents NIO's smart energy service platform, focusing on the NIO Power swap‑station business and detailing how time‑series forecasting is applied to predict demand, addressing complex seasonality, holiday drift, growth and competition, and describing the underlying machine‑learning and deep‑learning models and system architecture.
The article explains that database connection pools remain based on blocking I/O because JDBC was designed for BIO, managing session state per connection, and the ecosystem lacks a unified non‑blocking driver, making IO multiplexing technically possible but practically complex and rarely needed.
Although IO multiplexing can improve performance, Java applications typically use traditional connection pools like c3p0 or Tomcat because JDBC is built on blocking I/O, DB sessions require separate connections, and integrating NIO would complicate program architecture, making connection pools the pragmatic, mature solution.
Jetty’s ManagedSelector wraps the native NIO selector and, together with its ExecutionStrategy abstractions, merges I/O detection and handling in a single thread or adaptive pool, using strategies such as ProduceConsume, ProduceExecuteConsume, ExecuteProduceConsume, and EatWhatYouKill to maximize cache reuse and minimize context‑switch overhead in high‑concurrency applications.
Netty is a high‑performance, asynchronous, event‑driven NIO framework widely used in Java backend systems such as Dubbo and RocketMQ, and this article explains its fundamentals, key characteristics, architectural layers, high‑performance design, core components, and typical application scenarios across internet, gaming, and big‑data domains.
This article explains the three main Java I/O models—BIO (blocking), NIO (non‑blocking), and AIO (asynchronous)—detailing their characteristics, differences in blocking behavior, core components like Buffer, Channel, and Selector, and shows how they are applied in popular frameworks such as Netty, Mina, and Dubbo.
This article explains the concepts of synchronous vs asynchronous and blocking vs non‑blocking I/O, then details the characteristics, advantages, and drawbacks of Java’s three I/O models—BIO, NIO, and AIO—providing guidance on when to use each approach in backend development.
This article explains the concepts of synchronous vs asynchronous and blocking vs non‑blocking I/O, then compares Java's BIO, NIO, and AIO models, describing their mechanisms, advantages, drawbacks, and suitable usage scenarios for server‑side development.
This article demystifies the true reasons behind Redis's speed by exploring low‑level I/O mechanisms—from basic BIO to NIO and the Reactor model—explaining socket creation, connection handling, blocking behavior, and how Java’s non‑blocking APIs and system calls work together to achieve high‑throughput networking.
The article explains why Java applications typically use traditional database connection pools instead of IO multiplexing, covering JDBC’s blocking design, session management, ecosystem maturity, and the complexity of integrating non‑blocking I/O with existing frameworks, while noting that a non‑blocking implementation is technically feasible.
This technical presentation details NIO's evolution of OLAP solutions—from Druid and TiDB to Doris—explaining the selection criteria, Doris's advantages as a unified OLAP warehouse, its role in the CDP platform, practical deployment experiences, and lessons learned from real‑world usage.
This article explains the principle of zero‑copy, its role in improving I/O performance, and demonstrates how Java NIO, mmap, sendfile, channel‑to‑channel transfer, Netty composite buffers and other techniques achieve zero‑copy in backend systems.
This article introduces Netty, explains Java's BIO/NIO/AIO models, compares reactor threading architectures, details Netty's internal thread and handler pipeline design, and provides a complete example of building a high‑performance HTTP server with Netty.
The article explains that although IO multiplexing can improve performance, database access in Java typically relies on JDBC and connection pools, which are built on blocking I/O, making it difficult to combine DB connections with IO multiplexing without major architectural changes.