Algorithms/go-perfbook
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

expand on optimizing at different levels

Browse Source
This commit is contained in:
Damian Gryski 2018-01-05 12:28:00 -08:00
parent 3f14524242
commit 60bec2b464
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
performance.md
View File

@ -122,7 +122,10 @@ Anything that can be measured can be optimized. Make sure you're measuring
the right thing. Beware bad metrics. There are generally competing factors.
Good performance work requires knowledge at many different levels, from
system design, networking, hardware (CPU, caches, storage).
system design, networking, hardware (CPU, caches, storage), algorithms,
tuning, and debugging. With limited time and resources, consider which level
will give the most improvement: it won't always be algorithm or program
tuning.
This book is mostly going to talk about reducing CPU usage, reducing memory
usage, and reducing latency. It's good to point out that you can very rarely