《Understanding Software Dynamics》（Addison-Wesley 专业计算系列）第1版，Richard L. Sites 著（https://www.amazon.com/Understanding-Software-Addison-Wesley...）。这是一本新出的书，我还没看完……
Understanding Software Dynamics (Addison-Wesley Professional Computing Series) 1st Edition by Richard L. Sites (https://www.amazon.com/Understanding-Software-Addison-Wesley...) This is a recent book and I have not completed reading…
Richard Sites 写的《Understanding Software Dynamics》整本书都在讲性能优化 https://www.amazon.in/Understanding-Software-Addison-Wesley-...
The book Understanding Software Dynamics by Richard Sites is all about performance optimization https://www.amazon.in/Understanding-Software-Addison-Wesley-...
去通读一下 Richard Sites 写的《Understanding Software Dynamics》，把书里的例题都做一遍。你所描述的问题他全讲到了（L1/2/3 缓存命中率、它们对性能的影响、编译器优化如何……
Read through Understanding Software Dynamics by Richard Sites and work through the example problems in the book. He discusses exactly what you're describing (L1/2/3 cache hit rates, their performance implications, how compiler optimizations can…
…absolutely one of the most powerful tools I've used for deeply understanding performance bottlenecks (after isolating issues) such as poor scheduling behavior. I would highly recommend reading his book "Understanding Software Dynamics" [1] if you are interested in learning more about KUtrace or performance bottlenecks/optimizations in general. The book is quite dense and dives deep into the performance characteristics of many examples…
……给讨论补充点干货：你可以用来调试问题/找出薄弱点的工具是 tracer。这本由前 Google 资深工程师 Dick Sites 写的书深入讲解了这种 tracer 的设计与使用：《Understanding Software Dynamics》（书评：https://www.usenix.org/publications/loginonline/understandin...）
…contribution to the discussion: Something you could use to debug issues / detect weak points is a tracer. This book by Dick Sites (Early Google Engineer) goes over the design and use of such a tracer: Understanding Software Dynamics (review: https://www.usenix.org/publications/loginonline/understandin...)
《Understanding Software Dynamics》（Addison-Wesley 专业计算系列）第1版，Richard L. Sites 著（https://www.amazon.com/Understanding-Software-Addison-Wesley...）。这是一本新出的书，我还没看完……
Understanding Software Dynamics (Addison-Wesley Professional Computing Series) 1st Edition by Richard L. Sites (https://www.amazon.com/Understanding-Software-Addison-Wesley...) This is a recent book and I have not completed reading…
Richard Sites 写的《Understanding Software Dynamics》整本书都在讲性能优化 https://www.amazon.in/Understanding-Software-Addison-Wesley-...
The book Understanding Software Dynamics by Richard Sites is all about performance optimization https://www.amazon.in/Understanding-Software-Addison-Wesley-...
去通读一下 Richard Sites 写的《Understanding Software Dynamics》，把书里的例题都做一遍。你所描述的问题他全讲到了（L1/2/3 缓存命中率、它们对性能的影响、编译器优化如何……
Read through Understanding Software Dynamics by Richard Sites and work through the example problems in the book. He discusses exactly what you're describing (L1/2/3 cache hit rates, their performance implications, how compiler optimizations can…
他的书《Understanding Software Dynamics》是我读过最好的技术书之一。能排进我心目中的前三。
His book, "Understanding Software Dynamics", is one of the best technical books I've ever read. Top 3 for me.
……这绝对是我用过在定位问题后、深入理解性能瓶颈（比如糟糕的调度行为）最强大的工具之一。如果你有兴趣深入了解 KUtrace 或更广泛的性能瓶颈/调优，我强烈建议阅读他的书《Understanding Software Dynamics》[1]。这本书干货非常密集，深入剖析了许多例子的性能特征……
…absolutely one of the most powerful tools I've used for deeply understanding performance bottlenecks (after isolating issues) such as poor scheduling behavior. I would highly recommend reading his book "Understanding Software Dynamics" [1] if you are interested in learning more about KUtrace or performance bottlenecks/optimizations in general. The book is quite dense and dives deep into the performance characteristics of many examples…
……给讨论补充点干货：你可以用来调试问题/找出薄弱点的工具是 tracer。这本由前 Google 资深工程师 Dick Sites 写的书深入讲解了这种 tracer 的设计与使用：《Understanding Software Dynamics》（书评：https://www.usenix.org/publications/loginonline/understandin...）
…contribution to the discussion: Something you could use to debug issues / detect weak points is a tracer. This book by Dick Sites (Early Google Engineer) goes over the design and use of such a tracer: Understanding Software Dynamics (review: https://www.usenix.org/publications/loginonline/understandin...)