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

clarify "optimal cache wasn't worth it"

Browse Source
This commit is contained in:
Damian Gryski 2018-03-04 10:54:41 -08:00
parent d524aca4c2
commit 033e0f6595
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
performance.md
View File

@ -590,7 +590,7 @@ Cache common cases:
* Compare cost of cache logic to cost of refetching the data.
* A large cache can increase GC pressure and keep blowing processor cache.
I've done experiments with a network trace that showed even an optimal
I've done experiments with a network trace for a service that showed even an optimal
cache wasn't worth it. Your expected hit ratio is important. You'll want to
export the ratio to your monitoring stack. Changing ratios will show a
shift in traffic. Then it's time to revisit the cache size or the