Skip to content

Fix the memory usage part of doc #1724

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Merged
merged 2 commits into from
Jul 8, 2021
Merged

Fix the memory usage part of doc #1724

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f5d3b92
According to CHANGELOG.md#removed-apis. `TableLoadingMode` option is …
qichengzx Jul 7, 2021
614eadc
Remove `Options.ValueLogLoadingMode` part.
qichengzx Jul 8, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 0 additions & 4 deletions docs/content/get-started/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -626,14 +626,10 @@ Badger's memory usage can be managed by tweaking several options available in
the `Options` struct that is passed in when opening the database using
`DB.Open`.

- `Options.ValueLogLoadingMode` can be set to `options.FileIO` (instead of the
default `options.MemoryMap`) to avoid memory-mapping log files. This can be
useful in environments with low RAM.
- Number of memtables (`Options.NumMemtables`)
- If you modify `Options.NumMemtables`, also adjust `Options.NumLevelZeroTables` and
`Options.NumLevelZeroTablesStall` accordingly.
- Number of concurrent compactions (`Options.NumCompactors`)
- Mode in which LSM tree is loaded (`Options.TableLoadingMode`)
- Size of table (`Options.MaxTableSize`)
- Size of value log file (`Options.ValueLogFileSize`)

Expand Down