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

Merge pull request #1 from 0xflotus/patch-1

Browse Source 
fixed Similarly
This commit is contained in:
0xflotus 2019-05-07 09:25:52 +02:00 committed by GitHub
commit 166b5307e9
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
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

@ -1227,7 +1227,7 @@ different tradeoffs that were reasonable in the 70s or 80s but don't
necessarily apply to your use case. For example, what they determine to be
"reasonable" memory vs. disk usage tradeoffs. Memory sizes are now orders of
magnitude larger, and SSDs have altered the latency penalty for using disk.
Simiarly, some streaming algorithms are designed for router hardware, which
Similarly, some streaming algorithms are designed for router hardware, which
can make it a pain to translate into software.
Make sure the assumptions the algorithm makes about your data hold.