Skip to content

Commit

Permalink
Spelling
Browse files Browse the repository at this point in the history
Signed-off-by: Viktor Söderqvist <[email protected]>
  • Loading branch information
zuiderkwast committed Jul 5, 2024
1 parent 4d27f50 commit e73becb
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion topics/latency.md
Original file line number Diff line number Diff line change
Expand Up @@ -236,7 +236,7 @@ Fork time in different systems

Modern hardware is pretty fast at copying the page table.
So are modern hardware-assisted virtualized environments,
but fork can be really slow in older virtualized environmants without hardware support.
but fork can be really slow in older virtualized environments without hardware support.
As of 2024, this is hardly a problem.

You can measure the fork time for a Valkey instance by
Expand Down
2 changes: 1 addition & 1 deletion topics/lru-cache.md
Original file line number Diff line number Diff line change
Expand Up @@ -114,7 +114,7 @@ You can see three kind of dots in the graphs, forming three distinct bands.
In a theoretical LRU implementation we expect that, among the old keys, the first half will be evicted.
The Valkey LRU algorithm will instead only *probabilistically* evicts the older keys.

As you can see, Redis OSS 3.0 does a reasonalbe job with 5 samples.
As you can see, Redis OSS 3.0 does a reasonable job with 5 samples.
Using a sample size of 10, the approximation is very close to an exact LRU implementation.
(The LRU algorithm hasn't changed considerably since this test was performed, so the performance of Valkey is similar in this regard.)

Expand Down

0 comments on commit e73becb

Please sign in to comment.