From abd3ec035104a730db657acca82ee9eb5fca44d7 Mon Sep 17 00:00:00 2001 From: feiniks <36756310+feiniks@users.noreply.github.com> Date: Mon, 23 Jun 2025 14:42:13 +0800 Subject: [PATCH] Add fs_id_list_max_threads option (#538) Co-authored-by: yangheran --- manual/config/seafile-conf.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/manual/config/seafile-conf.md b/manual/config/seafile-conf.md index 6d709cdf..52b37a37 100644 --- a/manual/config/seafile-conf.md +++ b/manual/config/seafile-conf.md @@ -370,6 +370,12 @@ Go fileserver caches fs objects in memory. On the one hand, it avoids repeated c fs_cache_limit = 100 ``` +Since Pro 12.0.10 version, you can set the max threads of fs-id-list requests. When you download a repo, Seafile client will request fs id list, and you can control the maximum concurrency for handling fs-id-list requests in the go fileserver through `fs_id_list_max_threads` configuration, which defaults to 10. +``` +[fileserver] +fs_id_list_max_threads = 20 +``` + ## Profiling Go Fileserver Performance Since Seafile 9.0.7, you can enable the profile function of go fileserver by adding the following configuration options: