Course contentsShow
← Java
Lesson 1939 of 2,87039. File I/O: Basic Byte StreamsFree lesson

Performance Gains: Measuring Buffer Impact

Compare unbuffered vs buffered I/O performance: buffering often reduces execution time by 100x or more.

Performance Gains: Measuring Buffer Impact

You'll learn how buffering dramatically improves I/O performance by reducing the number of expensive disk operations.

The Cost of Unbuffered I/O

When you read or write files byte-by-byte using FileInputStream or FileOutputStream alone, each operation triggers a system call to the operating system. System calls are expensive—they involve context switching between your program and the kernel. Reading a 1MB file one byte at a time means 1 million system calls!

Buffering to the Rescue

When you wrap streams with BufferedInputStream or BufferedOutputStream, the buffer acts as a staging area. Instead of 1 million individual disk reads, you might perform just 128 reads (if using the default 8KB buffer). That's reducing system calls by a factor of 7,800!

Measuring the Difference

Here's the performance reality:

Unbuffered copy (1MB file, byte-by-byte):

  • 1 million read() calls
  • 1 million write() calls
  • Typical time: 2-5 seconds or more

Buffered copy (same file):

  • ~128 buffered read() operations
  • ~128 buffered write() operations
  • Typical time: 20-50 milliseconds

That's a 100-200x speedup for the same logical operation! Even with byte array copying (say, 1KB chunks), unbuffered I/O requires 1,000 system calls versus ~8 with buffering.

Why It Matters

Disk I/O is one of the slowest operations in computing. Every time you can batch multiple logical operations into a single physical disk access, you eliminate overhead. Buffering transforms I/O from a bottleneck into a manageable operation.

Key Takeaway: Buffering reduces system call overhead, often improving I/O performance by 100x or more—always use BufferedInputStream and BufferedOutputStream for file operations unless you have a specific reason not to.