I/O Impact of Multi-Thread Applications
This chapter provides tutorial notes and example codes on I/O impact of multi-thread Java applications. Topics include I/O intensive thread test class, FileEditor2.java; running multiple I/O threads on HotSpot and JRockit JVM.
These sections are omitted from this Web preview version. To view the full content,
see information on how to obtain the full version this book.
FileEditor.java - I/O Intensive Process
FileEditor.java - DK-4724038 JVM Bug
FileEditor2.java - Avoiding FileNotFoundException
MultithreadingIoRunner.java - Multiple I/O Threads
Performance of Multiple I/O Threads on HotSpot
Performance of Multiple I/O Threads on JRockit
- The maximum total productivity of a multi-thread I/O intensive application is limited by the hard disk
I/O operation execution power of computer hardware.
- Using the same number of threads as the number of processors on the computer
results the best productivity on I/O operations.
- Running multiple I/O intensive threads does not improve total productivity.
- JRockit R28.2.7 JVM has similar performance as HotSpot 1.7 JVM with I/O intensive threads.
- HotSpot JVM has a bug that prevent you open and close the same file repeatedly in short intervals.
Table of Contents
About This Book
JVM (Java Virtual Machine) Specification
Java HotSpot VM - JVM by Oracle/Sun
java.lang.Runtime Class - The JVM Instance
java.lang.System Class - The Operating System
ClassLoader Class - Class Loaders
Class Class - Class Reflections
JVM Runtime Data Areas
JVM Stack, Frame and Stack Overflow
Thread Testing Program and Result
CPU Impact of Multi-Thread Applications
►I/O Impact of Multi-Thread Applications
CDS (Class Data Sharing)
Micro Benchmark Runner and JVM Options
Micro Benchmark Tests on "int" Operations
Micro Benchmark Tests on "long" Operations
Micro Benchmark Tests in JIT Compilation Mode
Micro Benchmark Tests on "float" and "double" Operations
JRockit JVM 28.2.7 by Oracle Corporation
Full Version in PDF/EPUB