Hello,
I recently installed Seadrive on my Homeserver and have been pretty happy with it so far, especially how uploading a lot of files is pretty fast at least compared to nextcloud, which i used before. I am using the SeaDrive Client on Windows which has mostly worked fine so far, the only issue im noticing is that the up/download speed on single files is pretty slow (around 100-150mbps while i have a 1gbps connection between my PC and the Homeserver). I know that when up/downloading a lot of small files that would be slower than up/downloading a single big file but the big file up/downloads being so slow is something I didn’t expect. When downloading a file through the WebUI, i get the expected 100-110MB/s (~800mbps) download speed. Is there something i can/have to config that could make the up/download speed through the SeaDrive Client faster or is this expected/not fixable?
Also, i have all bandwidth limits in the SeaDrive client set to 0 (the default setting).
Hello @mistercoolertyper , are you uploading and downloading files in an encrypted library? And are you accessing the server via HTTP or HTTPS?
Additionally, when you upload files through the client, you can check the Nginx logs to see which requests are slower.
Hello, I am uploading through https and into a non-encrypted library. Where do i actually find the nginx logs? I haven’t worked with nginx or anything a lot before. Also I’m running Seafile in a Docker container using the Seafile-12 Image i found on the apps tab in unraid.
Hello @mistercoolertyper ,
you can find the nginx logs inside the seafile container at the following path: /var/log/nginx/seafhttp.access.log.
Hello @feiniks ,
I have checked the logs while up and downloading a 5GB test file created by running
fsutil file createnew test 5369000000
on windows.
These were while Uploading from the SeaDrive Client, which was actually pretty fast (around 400mbps when checking network traffic from SeaDrive in TaskManager):
192.168.178.10 172.25.1.5 [27/Apr/2025:11:04:25 -0700] "PUT /seafhttp/repo/e4ac0ac6-d233-48f7-abdd-5c1125b0d83a/block/8c206a1a87599f532ce68675536f0b1546900d7a HTTP/1.1" 200 0 "-" "SeaDrive/3.0.13 (Windows NT)" 0.090
192.168.178.10 172.25.1.5 [27/Apr/2025:11:04:25 -0700] "PUT /seafhttp/repo/e4ac0ac6-d233-48f7-abdd-5c1125b0d83a/block/8c206a1a87599f532ce68675536f0b1546900d7a HTTP/1.1" 200 0 "-" "SeaDrive/3.0.13 (Windows NT)" 0.100
192.168.178.10 172.25.1.5 [27/Apr/2025:11:04:25 -0700] "PUT /seafhttp/repo/e4ac0ac6-d233-48f7-abdd-5c1125b0d83a/block/8c206a1a87599f532ce68675536f0b1546900d7a HTTP/1.1" 200 0 "-" "SeaDrive/3.0.13 (Windows NT)" 0.090
192.168.178.10 172.25.1.5 [27/Apr/2025:11:04:26 -0700] "PUT /seafhttp/repo/e4ac0ac6-d233-48f7-abdd-5c1125b0d83a/block/8c206a1a87599f532ce68675536f0b1546900d7a HTTP/1.1" 200 0 "-" "SeaDrive/3.0.13 (Windows NT)" 0.099
192.168.178.10 172.25.1.5 [27/Apr/2025:11:04:26 -0700] "PUT /seafhttp/repo/e4ac0ac6-d233-48f7-abdd-5c1125b0d83a/block/8c206a1a87599f532ce68675536f0b1546900d7a HTTP/1.1" 200 0 "-" "SeaDrive/3.0.13 (Windows NT)" 0.095
192.168.178.10 172.25.1.5 [27/Apr/2025:11:04:26 -0700] "PUT /seafhttp/repo/e4ac0ac6-d233-48f7-abdd-5c1125b0d83a/block/8c206a1a87599f532ce68675536f0b1546900d7a HTTP/1.1" 200 0 "-" "SeaDrive/3.0.13 (Windows NT)" 0.095
192.168.178.10 172.25.1.5 [27/Apr/2025:11:04:26 -0700] "PUT /seafhttp/repo/e4ac0ac6-d233-48f7-abdd-5c1125b0d83a/block/8c206a1a87599f532ce68675536f0b1546900d7a HTTP/1.1" 200 0 "-" "SeaDrive/3.0.13 (Windows NT)" 0.096
192.168.178.10 172.25.1.5 [27/Apr/2025:11:04:27 -0700] "PUT /seafhttp/repo/e4ac0ac6-d233-48f7-abdd-5c1125b0d83a/commit/HEAD/?head=32811e0502ab3e0c4100bd7a233fd7e54fed3c6d HTTP/1.1" 200 0 "-" "SeaDrive/3.0.13 (Windows NT)" 0.343
192.168.178.10 172.25.1.5 [27/Apr/2025:11:04:27 -0700] "GET /seafhttp/repo/e4ac0ac6-d233-48f7-abdd-5c1125b0d83a/commit/HEAD HTTP/1.1" 200 81 "-" "SeaDrive/3.0.13 (Windows NT)" 0.002
(also, this is just the last few lines of the log since i didn’t want to paste a couple houndred lines of the same message in here)
The Upload over the WebUI was slower and i didn’t check the logs after that one because i dont mind the slow Upload speed over the WebUI, since i usually only upload through the SeaDrive Client.
The log when Downloading through the WebUI only showed one request, which was this: 192.168.178.10 172.25.1.5 [27/Apr/2025:11:07:20 -0700] "GET /seafhttp/repos/e4ac0ac6-d233-48f7-abdd-5c1125b0d83a/files//test/?op=download HTTP/1.1" 200 5369000000 "https://seafile.mydomain.com/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:137.0) Gecko/20100101 Firefox/137.0" 46.618 and has speeds around ~110MB/s so ~880mbps.
When Downloading that same file through the SeaDrive Client, the log showed these messages:
192.168.178.10 172.25.1.5 [27/Apr/2025:11:08:19 -0700] "GET /seafhttp/repo/e4ac0ac6-d233-48f7-abdd-5c1125b0d83a/block/8c206a1a87599f532ce68675536f0b1546900d7a HTTP/1.1" 200 10485760 "-" "SeaDrive/3.0.13 (Windows NT)" 0.079
192.168.178.10 172.25.1.5 [27/Apr/2025:11:08:19 -0700] "GET /seafhttp/repo/e4ac0ac6-d233-48f7-abdd-5c1125b0d83a/block/8c206a1a87599f532ce68675536f0b1546900d7a HTTP/1.1" 200 10485760 "-" "SeaDrive/3.0.13 (Windows NT)" 0.079
192.168.178.10 172.25.1.5 [27/Apr/2025:11:08:19 -0700] "GET /seafhttp/repo/e4ac0ac6-d233-48f7-abdd-5c1125b0d83a/block/8c206a1a87599f532ce68675536f0b1546900d7a HTTP/1.1" 200 10485760 "-" "SeaDrive/3.0.13 (Windows NT)" 0.074
192.168.178.10 172.25.1.5 [27/Apr/2025:11:08:19 -0700] "GET /seafhttp/repo/e4ac0ac6-d233-48f7-abdd-5c1125b0d83a/block/8c206a1a87599f532ce68675536f0b1546900d7a HTTP/1.1" 200 10485760 "-" "SeaDrive/3.0.13 (Windows NT)" 0.062
192.168.178.10 172.25.1.5 [27/Apr/2025:11:08:19 -0700] "GET /seafhttp/repo/e4ac0ac6-d233-48f7-abdd-5c1125b0d83a/block/8c206a1a87599f532ce68675536f0b1546900d7a HTTP/1.1" 200 10485760 "-" "SeaDrive/3.0.13 (Windows NT)" 0.071
192.168.178.10 172.25.1.5 [27/Apr/2025:11:08:19 -0700] "GET /seafhttp/repo/e4ac0ac6-d233-48f7-abdd-5c1125b0d83a/block/8c206a1a87599f532ce68675536f0b1546900d7a HTTP/1.1" 200 10485760 "-" "SeaDrive/3.0.13 (Windows NT)" 0.061
192.168.178.10 172.25.1.5 [27/Apr/2025:11:08:19 -0700] "GET /seafhttp/repo/e4ac0ac6-d233-48f7-abdd-5c1125b0d83a/block/8c206a1a87599f532ce68675536f0b1546900d7a HTTP/1.1" 200 10485760 "-" "SeaDrive/3.0.13 (Windows NT)" 0.062
192.168.178.10 172.25.1.5 [27/Apr/2025:11:08:20 -0700] "GET /seafhttp/repo/e4ac0ac6-d233-48f7-abdd-5c1125b0d83a/block/8c206a1a87599f532ce68675536f0b1546900d7a HTTP/1.1" 200 10485760 "-" "SeaDrive/3.0.13 (Windows NT)" 0.068
192.168.178.10 172.25.1.5 [27/Apr/2025:11:08:20 -0700] "GET /seafhttp/repo/e4ac0ac6-d233-48f7-abdd-5c1125b0d83a/block/8c206a1a87599f532ce68675536f0b1546900d7a HTTP/1.1" 200 10485760 "-" "SeaDrive/3.0.13 (Windows NT)" 0.056
192.168.178.10 172.25.1.5 [27/Apr/2025:11:08:20 -0700] "GET /seafhttp/repo/e4ac0ac6-d233-48f7-abdd-5c1125b0d83a/block/8c206a1a87599f532ce68675536f0b1546900d7a HTTP/1.1" 200 10485760 "-" "SeaDrive/3.0.13 (Windows NT)" 0.078
and the speeds while downloading were even slower than when Uploading (~50-~100mbps).
I’m guessing this is because the client uses multiple requests to download the file in Chunks while the WebUI uses one singular requests but is there any way i could maybe make the Chunks larger to potentially increase download speed?
I don’t mind not having the full ~880mbps download speed from the SeaDrive Client but around like 400mbps or so would be nice to have since that’s already a pretty big improvement over the ~50-100mbps I’m currently getting while downloading through the Desktop Client.
Hi @mistercoolertyper ,
since each block is 8MB in size, and based on the nginx logs, the download speed for each block can generally reach the expected level.
Therefore, the issue may be due to the client downloading blocks non-sequentially rather than continuously downloading the entire file. When there is a relatively large amount of bandwidth available, TCP’s sliding window may prevent achieving the expected speed. Currently, there may not be a good way to optimize this.
Hello @feiniks ,
Yeah that makes sense, I will just stick to downloading very large files through the WebUI then when I have to download really big files.
Still, thanks for the help though!