mirror of
https://github.com/seaweedfs/seaweedfs.git
synced 2024-01-19 02:48:24 +00:00
Updated Directories and Files (markdown)
parent
16212899e2
commit
fd7ac55358
|
@ -4,6 +4,8 @@ When talking about file systems, many people would assume directories, list file
|
|||
|
||||
### Sample usage
|
||||
|
||||
First, run ```weed filer -h``` to see an example ```filer.toml``` file. Copy it out and read it, create the data store if needed.
|
||||
|
||||
Two ways to start a weed filer
|
||||
|
||||
```bash
|
||||
|
@ -74,9 +76,9 @@ Here is a comparison of different filer store options.
|
|||
|
||||
1. "memory" : only for testing/example purpose.
|
||||
2. "leveldb": simple, single machine, fast, scalable, but no failover.
|
||||
3. "mysql"/"postgres": robust and common, fast enough for most cases, scalable.
|
||||
4. "cassandra": robust and common, fast, scalable.
|
||||
5. "redis": very fast, scalable with clustering, need to enable persistent storage, file listing is limited as one directory's sub file names are stored in one set of a key.
|
||||
3. "mysql"/"postgres": robust and well-understood, fast enough for most cases, scalable.
|
||||
4. "cassandra": robust and well-understood, fast, scalable.
|
||||
5. "redis": very fast, scalable with clustering, need to enable persistent storage, file listing is limited because one directory's sub file names are stored in one key~value entry.
|
||||
|
||||
### Extending Storage Options
|
||||
|
||||
|
|
Loading…
Reference in a new issue