mirror of
https://github.com/seaweedfs/seaweedfs.git
synced 2024-01-19 02:48:24 +00:00
Updated FAQ (markdown)
parent
dbec9a3b18
commit
6f06bb10b6
2
FAQ.md
2
FAQ.md
|
@ -54,7 +54,7 @@ It is also important to leave some disk space for a couple of volume size, so th
|
|||
|
||||
If one volume has large number of small files, the memory usage would be high in order to keep each entry in memory or in leveldb.
|
||||
|
||||
To reduce memory usage, one way is to convert the older volumes into Erasure-Coded volumes, which are read only. The volume server can will sort the index and store it as a sorted index file (with extension `.sdx`). So looking up one entry costs a binary search within the sorted index file, instead of O(1) memory lookup.
|
||||
To reduce memory usage, one way is to convert the older volumes into [Erasure-Coded volumes](https://github.com/chrislusf/seaweedfs/wiki/Erasure-Coding-for-warm-storage), which are read only. The volume server can will sort the index and store it as a sorted index file (with extension `.sdx`). So looking up one entry costs a binary search within the sorted index file, instead of O(1) memory lookup.
|
||||
|
||||
### How to configure volumes larger than 30GB?
|
||||
|
||||
|
|
Loading…
Reference in a new issue