Perhaps a cache bypass would help with the performance issue. More details here.
Self-Hosted Main
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
For Example
- Service: Dropbox - Alternative: Nextcloud
- Service: Google Reader - Alternative: Tiny Tiny RSS
- Service: Blogger - Alternative: WordPress
We welcome posts that include suggestions for good self-hosted alternatives to popular online services, how they are better, or how they give back control of your data. Also include hints and tips for less technical readers.
Useful Lists
- Awesome-Selfhosted List of Software
- Awesome-Sysadmin List of Software
Cloudflare Tunnel's cloudflared links your home to two closest data centres and so should (?) be quicker, but response times would depend on where a user is accessing your service from.
However, given residential ISP speeds and peering in most parts of the world you'd be unlikely to notice any real difference between the two and other than that 'last leg' access tech the processing within Cloudflare's flow is the same whether you use cloudflared or direct proxying.
Fair point, I don't remember whether my plan was 1000/1000 or 1000/100. Anyways, you are probably right about the difference in performance between Tunnel and Proxy doesn't matter here
Unrelated, how do you have 50 gigs of ram? It's not divisible by 4?
My total ram in MiBs (Mebibytes) are 48087. The rest is math shenanigans. Portainer on the othehand shows my RAM memory as 50.6 GB (Gigabytes). So you can do the math and verify the translations ;)
Ah just portainer being strange then.
Mine also overreports
RAM doesn't need to be divisible by 4. You can mix and match sizes of RAM it's just not advisable.
I don't believe ddr4/5 are available in 2gb sticks, so everything would be divisible by 4 - a mixture of 4/8/16gb dimms
Sounds like the issue is with your setup. Not Cloudflare. Figure out why android is double uploading.
I just did some digging around, and it looks like it's a common known issue for the android client:
https://github.com/nextcloud/android/issues/11906
I guess i'd just deal with it for now, hopefully this gets resolved soon.