-
```
Some stats programs have things like kmer (with -K) reports and probe-id
counting (with -D).
These programs can consume a lot of RAM (>10GB), even with the highly efficient
sparsehash library o…
-
```
Some stats programs have things like kmer (with -K) reports and probe-id
counting (with -D).
These programs can consume a lot of RAM (>10GB), even with the highly efficient
sparsehash library o…
-
```
Some stats programs have things like kmer (with -K) reports and probe-id
counting (with -D).
These programs can consume a lot of RAM (>10GB), even with the highly efficient
sparsehash library o…
-
```
Some stats programs have things like kmer (with -K) reports and probe-id
counting (with -D).
These programs can consume a lot of RAM (>10GB), even with the highly efficient
sparsehash library o…
-
## Motivation
Currently, we have a limit of N=128 block ranges (or 1028 blocks after #2493) with LRU eviction. This is OK, but we could evict many pages at once, resulting in a relatively high over…
-
```
Some stats programs have things like kmer (with -K) reports and probe-id
counting (with -D).
These programs can consume a lot of RAM (>10GB), even with the highly efficient
sparsehash library o…
-
```
Some stats programs have things like kmer (with -K) reports and probe-id
counting (with -D).
These programs can consume a lot of RAM (>10GB), even with the highly efficient
sparsehash library o…
-
```
Some stats programs have things like kmer (with -K) reports and probe-id
counting (with -D).
These programs can consume a lot of RAM (>10GB), even with the highly efficient
sparsehash library o…
-
```
Some stats programs have things like kmer (with -K) reports and probe-id
counting (with -D).
These programs can consume a lot of RAM (>10GB), even with the highly efficient
sparsehash library o…
-
```
Some stats programs have things like kmer (with -K) reports and probe-id
counting (with -D).
These programs can consume a lot of RAM (>10GB), even with the highly efficient
sparsehash library o…