Java Performance Optimization in Plain Terms
Tags
Summary
Editor's review
Who it's for
A good fit for
- 有两三年 Java 开发经验、想系统补齐性能调优知识地图的工程师
- 负责线上系统稳定性、经常处理接口变慢与内存问题的后端开发
- 准备面试或技术评审,需要梳理 JVM、并发、代码优化要点的读者
- 计算机专业高年级学生与培训学员,希望从代码层过渡到系统层理解性能
Not a good fit for
- 完全没有 Java 基础、连线程与对象模型都不熟悉的纯新手
- 只想找一份可直接套用的 JVM 参数模板的读者
- 需要覆盖 JDK 11 以后新特性与云原生可观测性体系的读者
Reading tips
- 先通读第1章建立优化目标与衡量指标的概念,避免陷入盲目调参
- 第3章建议对照自己的代码库阅读,边读边改几个热点方法,效果最好
- 第6、7章可结合线上监控工具实操,用真实压测数据验证书中的结论
- 遇到与当前 JDK 版本不符的内容时,以官方文档和实测结果为准
About the publisher
The Publishing House of Electronics Industry is a comprehensive publisher distinguished by its focus on electronic information and related fields. Judging from the more than 3,000 titles in its catalogue, its publishing covers programming and design, artificial intelligence, computer science, finance and economics, photography, and social sciences, attending both to cutting-edge technology and to general readers. Representative titles include Factor Investing: Methods and Practice, x86 Assembly Language: From Real Mode to Protected Mode, The RISC-V Reader, Artificial Intelligence: Speech Recognition, Understanding and Practice, Phased Array Radar Technology, Radar Target Characteristics, and 100 Go Mistakes and How to Avoid Them, most of which centre on technical methods and engineering practice. Its authors include Shi Chuan, Li Zhong, Wang Xiaobo, David Patterson, Andrew Waterman, and Yu Zihao, among others from China and abroad. Owing to limited public information, no further publishing features are elaborated here.
Contents
- Chapter 1 Overview of Performance Tuning Strategies
- 1.1 Why Tuning Is Needed
- 1.2 Reference Factors for Performance Optimization (Divergences in Traditional Computer Architecture, Computing Resources That Cause System Bottlenecks, Program Performance Metrics, Performance Optimization Goals, Performance Optimization Strategies)
- 1.3 Classification Methods for Performance Tuning (Business, Foundational Technology, Components, Architecture, Layers)
- 1.4 Chapter Summary
- Chapter 2 Preparatory Knowledge Before Optimization
- 2.1 Server Knowledge (Memory, GPU/CPU, Hard Disks, Network Architecture)
- 2.2 Emerging Technologies
- Chapter 3 Java API Call Optimization Suggestions
- 3.1 Object-Oriented and Primitive Types (Creating Objects with Clone(), Avoiding boolean Checks, Using Conditional Operators More, Static Methods Instead of Instance Methods, Conditional Use of final, Avoiding Unnecessary instanceof, Using Local Variables More, Bitwise Operations, One-Dimensional Arrays Instead of Two-Dimensional Arrays, etc.)
- Chapter 4 Program Design Optimization Suggestions
- Chapter 5 Java Parallel Program Optimization Suggestions
- Chapter 6 JVM Performance Testing and Monitoring
- Chapter 7 JVM Performance Tuning Suggestions
- Chapter 8 Other Optimization Suggestions
FAQ
这本书主要讲 JVM 调优吗?
零基础能直接读这本书吗?
2016 年出版的书现在还适用吗?
书中案例是真实项目吗?
Comments
Find this book
This site is an index: you start “Search all sources” in your browser, and the entries it lists all point to third-party sites; please judge their availability yourself.
About the author
Zhou Mingyao is an author about whom limited public information is available; the library currently holds only one work by him, Deep Understanding of the JVM & G1 GC. Judging from the subject of this representative book, the author focuses on the internal mechanisms of the Java Virtual Machine and garbage collection technology, a writing direction within programming and design that leans toward system-level and principle-oriented topics. The book centers on the JVM and the G1 garbage collector and addresses developers who wish to understand runtime behavior in depth, showing clear technical depth and a focused, topic-specific approach. Based on the available information, Zhou Mingyao's writing style tends toward analysis of underlying principles rather than broad introductory overviews, making the book suitable for readers with some foundation. Owing to limited materials, details of his life, professional background, and other works cannot be confirmed, and readers may understand his technical focus through the work itself.