Nextcloud speed auf 50mbit/s limitiert?
Hey,
Zuhause betreibe ich einen Raspberry Pi 5, der als Host für meine Nextcloud dient. Soweit läuft alles reibungslos. Allerdings ist mir aufgefallen, dass die Upload-Geschwindigkeit nie über 60 Mbit/s liegt. Dies überrascht mich, da meine Internetverbindung theoretisch bis zu 250 Mbit/s erreichen kann. Aktuell bin ich sogar über ein LAN-Kabel mit demselben Netzwerk verbunden, was bedeuten sollte, dass die Übertragungsgeschwindigkeit sogar 1 Gbit/s beträgt.
Kennt jemand dieses Problem?
Vielen dank.
(1 votes)
Loading...
Look at your rate at the internet provider, even with glass fiber, the upload is often lower, for example, at Deutsche Telekom 50 MBit, which would come down.
If you transmit the data in the LAN and then also use the local IP of the Pi (so it does not only run over the router and the Internet connection) it should be faster.
If that’s not the case, try what write rate your SSD/plate at the Pi creates.
So I know I have 250 up and 250 down, by Speedtest and since I know my contract. Do not use Telekom or the like. You won’t know because I live in Italy.
However, you happen to know how I can see how fast my HDD can work, because it is not faster about the Locale IP.
Write a big file on it with dd… is the easiest thing I just remember
dd if=/dev/zero of=/path/to/mountpoint/new_file bs=8k count=1000
then delete the file stop again.
Okay many thanks for your efforts.
Have tested everything again, but it is limited at 50mbit/s.
Can’t help me, I’m a carved vi user 🙂 M-B could be Alt-B, “M” is the meta key. I’m sorry to have to leave now, I’m gonna have to go to work tomorrow. After changing the php.ini, you need to restart the web server or php-fpm process so that it becomes effective…
Boah I hate nano…. I can look for something with ctrl but there I stand can go back with M-B but wieeee omg xd
upload_max_filesize and post_max_size , see 3 comments…
Got her, what should I look for because chunk give a lot
Don’t try /etc/php/ and then under any mod or fpm depending on how it works…
You happen to know where it is, don’t know every path by heart.
Look into the php.ini on the server, which is the maximum, more the client cannot upload per Chunk…
upload_max_filesize and post_max_size are the options… put the hold on 100M or so…
Aso thought on the raspi xd. Yes, they sounded, but didn’t change anything, they had to add the line because it didn’t execute.
The LimitRequestBody is default 0, so disabled…
Can’t find my nextcloud.cfg somehow…
The client takes default 10 MB Chunks, which can be customized by .cfg. https://docs.nextcloud.com/desktop/3.2/advancedusage.html?highlight=chunk May not be larger than the PHP max_upload_size / max_post_size on the server. Ggfs. let’s see if it’s sufficiently large.
It can be that the web server still has an option somewhere, how big an upload can be maximum… LimitRequestBody at Apache
No, so I don’t use the browser, but also just I used the Nextcloud app also Arch.Have tested the browser, get the similar value.
Still a question, what do you take as a client to upload? In the browser, the Chunked uploads, so always uploads 1MB (e.g.) blocks by JS and then assembles them on server side. Depending on the browser and speed of the client there can also be a bottleneck.
Unfortunately, this is difficult to analyze.
111 MB/s is now also not a restriction. It’s not like that. If you run the btop during an upload, the processor load is on the stop (possibly due to TLS)?
that is the output: 1000+0 records in
1000+0 records out
1048576000 bytes (1.0 GB, 1000 MiB) copied, 9.41363 s, 111 MB/s
So I’ll do it with dd.
PS: At dd NOT take /dev/sda, but mountpoint, otherwise you overwrite your plate….
I used hdparm, but I’m right, I didn’t think it’s worth reading, a second I’m looking for a tool:)
The stupid thing about smartctl is that it only tests reading, SSDs are often much slower when writing than reading…
Thank you, you just found a tool, which gives me the speed:
/dev/sda1:
Timing cached reads: 9758 MB in 2.00 seconds = 4883.57 MB/sec
Timing buffered disk reads: 490 MB in 3.01 seconds = 162.77 MB/sec
So my HDD is not the problem. :/
And how is the used storage medium connected?
SSD via the M.2-HAT, which is then connected via PCIe2.0 x1 and thus cannot exceed the limit of PCIe2.0 x1 (at 0.5GBit/s).
No, unfortunately not, had no SSD, so I use an HDD via USB, which should be faster.
What files are you uploading?
if you upload images, you will probably limit the HDD. The write and read rates are massively breaking one in many small files.
and see how much CPU is used on the pi during an upload and for what. If wait io is in the double-digit percentage range, is probably the hdd of the bottleneck.
Have tested the HDD that is fast enough, my Raspi is also only loaded at 10% and there are actually all possible files like zb: text files images etc.
Your tests have all only tested sequential reading and writing. This is not comparable to the upload of quite small files.
Upload a large file with at least 1 Gb and see if it goes faster.