Live data from Hacker News

Nextcloud Hub 26 Spring: Built together, designed for the future

nextcloud.com

41–50 of 103 posts

Re: Nextcloud Hub 26 Spring: Built together, designed for the future

#41
post #23
post #12

I run Nextcloud at home with 1.5TB of files and 2 users, on a reasonably sized server. It is painfully slow. Still better than OneDrive, but only just: synscing takes forever, never reaching a fraction of available bandwidth. Upload from my phone is flaky, often hangs and needs manual intervention. It is a battery drain. The whole experience with add-ons and the general UI feels like a 2010 PHP app. I am grateful Nex…

This seems to be a really common issue with NextCloud. I'd say about 30% of installs seems to just..be slow? I've had this happen to me on a handful of installs, and i've had friends/collegues it's happened to. I'm not aware of any "Fix" besides whiping your install(s) and trying again. Try not to use a backup if you can, as it can keep the slowness/lag across installs. It's really annoying.

Opencloud is the golang rewrite and is much faster.

Re: Nextcloud Hub 26 Spring: Built together, designed for the future

#42

I love Nextcloud but I feel like they should really completely redo their UI. It just doesn't look like something from this decade.

Wait, you don't feel so? I have maintained a Nextcloud server for a small business for the last 6 years. I agree when I started using it early 2020 that the ui felt less modern, but after some updates down the road up until now it looks completely like it is from this era. Am I missing something? However, I never complained about the UI neither then nor now.

NextCloud's macOS app is implemented in a way that completely disregards any UI guidelines or just common sense for the platform.

Developers either don't use macOS at all, or don't care.

But functionally it works for our small team.

Re: Nextcloud Hub 26 Spring: Built together, designed for the future

#43
post #23
post #12

I run Nextcloud at home with 1.5TB of files and 2 users, on a reasonably sized server. It is painfully slow. Still better than OneDrive, but only just: synscing takes forever, never reaching a fraction of available bandwidth. Upload from my phone is flaky, often hangs and needs manual intervention. It is a battery drain. The whole experience with add-ons and the general UI feels like a 2010 PHP app. I am grateful Nex…

This seems to be a really common issue with NextCloud. I'd say about 30% of installs seems to just..be slow? I've had this happen to me on a handful of installs, and i've had friends/collegues it's happened to. I'm not aware of any "Fix" besides whiping your install(s) and trying again. Try not to use a backup if you can, as it can keep the slowness/lag across installs. It's really annoying.

At that point it would be so painful it'd prompt users to switch to competing software.

The whole NextCloud suite seems to have this problem of too many offerings that don't get polished to completion.

Re: Nextcloud Hub 26 Spring: Built together, designed for the future

#44

I left nextcloud because how slow it felt even on my beefy server. I switched to opencloud.eu, it might have less features but it's just what I needed

Seriously. I ran it on a server with two Xeon CPUs and 128GB of RAM. The web interface took minutes to do anything. Browsing a large photo library was just completely unworkable (and that was before they ripped out all the sorting and filtering features from the photo library).

My instance killed itself somehow, likely a failed auto update. I was, of course, using the default docker setup with the watchtower instance etc etc. I never got it to come back up, and I haven't missed it at all.

Even opening the damn login page took a good 30 seconds to load, there's no excuse for this kind of performance on a real-deal enterprise server.

Re: Nextcloud Hub 26 Spring: Built together, designed for the future

#45
post #20
post #14

Earlier quoted context omitted.

Nextcloud is written in PHP, which doesn't sound scalable to me. OwnCloud is written in Go but employs an open-core model. Some features are locked behind a proprietary paywall.

> Nextcloud is written in PHP, which doesn't sound scalable to me. Lol what? Facebook (pre Hack), Tumblr, Wordpress, Etsy...

Nextcloud and Wordpress both suffer massively from technical debt.

Re: Nextcloud Hub 26 Spring: Built together, designed for the future

#46
post #26

If I want to buy a small NAS that just runs Nextcloud and has a copy of my Google Photos library - what do I go with? I don't have a ton of space so something that fits in the media center.

GMKTec G9. Four NVMe slots, plus some internal memory to deploy TrueNAS. It only has 12GB of RAM, but has two ethernet cards, acceptable cooling and performance and has a small footprint. SSDs shall be single sided and gonna need heatsinks, but I believe it works well and is not tied to any manufacturer for anything. If you want go all-out get ASUSTOR's Ryzen based systems. You can use the stock firmware or disable i…

I have a g9 and cooling is fine, but not great. I ended up opening it up and placing heatsinks on hot chips

Re: Nextcloud Hub 26 Spring: Built together, designed for the future

#47

I left nextcloud because how slow it felt even on my beefy server. I switched to opencloud.eu, it might have less features but it's just what I needed

Seriously. I ran it on a server with two Xeon CPUs and 128GB of RAM. The web interface took minutes to do anything. Browsing a large photo library was just completely unworkable (and that was before they ripped out all the sorting and filtering features from the photo library). My instance killed itself somehow, likely a failed auto update. I was, of course, using the default docker setup with the watchtower instance…

NextCloud needs tuning (mostly of php-fpm and caching ) oob to be fast/usable in my experience. Just throwing resources at it won't make it faster as the defaults are generally quite conservative.

They even have a specific guide for this topic, https://docs.nextcloud.com/server/stable/admin_manual/instal...

As a side note, it's PHP so your single core clocks will generally be more relevant for latency than multi-core performance, feeding many cores requires a lot of divisble work.

Re: Nextcloud Hub 26 Spring: Built together, designed for the future

#48
post #42

Earlier quoted context omitted.

Wait, you don't feel so? I have maintained a Nextcloud server for a small business for the last 6 years. I agree when I started using it early 2020 that the ui felt less modern, but after some updates down the road up until now it looks completely like it is from this era. Am I missing something? However, I never complained about the UI neither then nor now.

NextCloud's macOS app is implemented in a way that completely disregards any UI guidelines or just common sense for the platform. Developers either don't use macOS at all, or don't care. But functionally it works for our small team.

NextCloud generally appears to use their own design system everywhere, Android apps are also not in Material or on iOS (iirc) in Cupertino. It makes for a subpar experience in general but is consistent.

Re: Nextcloud Hub 26 Spring: Built together, designed for the future

#49
I love nextcloud and have been using it for years. However recently I've considered taking my instance offline or at least behind a VPN because even if only 10% is true of what AI folks are claiming about LLMs finding exploits left and right, it seems super risky to be hosting your private data on nextcloud.

How do you folks deal with these massively increased threats to self-hosted open source apps?

Re: Nextcloud Hub 26 Spring: Built together, designed for the future

#50
post #18

Nextcloud is great, I self-host an instance at home. I mostly use the calendar, address book, and file sharing with links a la Google Drive. It's probably heavier and slower than it should be for what it does, but it works. Just like Home Assistant, it is a "must have" tool for self-hosters.

What's your experience like?

Lot's of people say that's a mess to maintain and too broken to actively use.

I often doubt if that's due to actual problems, or mix with that and bad decisions on the setup. Is dockering, keeping the data handling itself outside of it and a few other easy (or not so much) precautions enough to have a somewhat smoother sailing?

Also, how much time do you need to keep things from failing apart?

Post reply on HN