add use_block_cache and seaf-gc --rm-fs (#37)

* add use_block_cache and seaf-gc --rm-fs

* improve doc

* improve doc
This commit is contained in:
Xiangyue Cai 2021-07-20 14:55:07 +08:00 committed by GitHub
parent 2c6945d8ce
commit 0ec7a552f2
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 19 additions and 0 deletions

View File

@ -142,6 +142,16 @@ max_sync_file_count = 100000
fs_id_list_request_timeout = 300
```
New in Seafile Pro 8.0.5: If you use cloud storage backend, you can enable the `use_block_cache` configuration to speed up file access. `use_block_cache` the default value is false. Note that this configuration is only effective for downloading files through web page or API, not for synchronized files. The `block_cache_size_limit` configuration is used to limit the size of the cache. `block_cache_size_limit` the default value is 10GB. the `block_cache_file_types` configuration is used to limit the file types that are cached. `block_cache_file_types` the default value is mp4;mov.
```
[fileserver]
use_block_cache = true
# Set block cache size limit to 100MB
block_cache_size_limit = 100
block_cache_file_types = mp4;mov
```
## Database configuration
The whole database configuration is stored in the `[database]` section of the configuration file, whether you use SQLite, MySQL or PostgreSQL.

View File

@ -92,6 +92,15 @@ seaf-gc.sh -r
**In Seafile version 4.1.1 and later, libraries deleted by the users are not immediately removed from the system. Instead, they're moved into a "trash" in the system admin page. Before they're cleared from the trash, their blocks won't be garbage collected.**
### Removing FS objects
Since Pro server 8.0.6, you can remove garbage fs objects. It should be run without the --dry-run option:
```
seaf-gc.sh --rm-fs
```
### Using Multiple Threads in GC
Since Pro server 5.1.0, you can specify the thread number in GC. By default,