Live data from Hacker News

Why Nextcloud feels slow to use

ounapuu.ee

111–120 of 359 posts

Re: Why Nextcloud feels slow to use

#111
post #70

Earlier quoted context omitted.

I found copyparty to be too busy on the UI/UX side of things. I've settled on dufs[0], quick to deploy, fast to use use, and cross platform. [0] https://github.com/sigoden/dufs

Do you have a systemd for it, run it with Docker, or simply manually as needed? I find its simplicity perfect!

I run it manually as needed. It's already packaged for both Alpine Linux and Homebrew which suits my ad-hoc needs wonderfully!

Re: Why Nextcloud feels slow to use

#112

Nextcloud server is written in PHP. Of course it is slow. It's also designed to be used as an office productivity suite meaning a lot of features you may not actually use are enabled by default and those services come with their own cronjobs and so on.

PHP is super-fast today. I've built 2 customer facing web products with PHP which made each a million dollar business. And they were very fast!

https://dev.to/dehemi_fabio/why-php-is-still-worth-learning-...

Re: Why Nextcloud feels slow to use

#113

I don't doubt that large amounts of javascript can often cause issues but even when cached NextCloud feels sluggish. When I look at just the network tab of a refresh of the calendar page it does 124 network calls, 31 of which aren't cached. it seems to be making a call per calendar each of which is over 30ms. So that stacks up the more calendars you have(and you have a number by default like contact birthdays). The J…

I was going to say... The size of the JS only matters the first time you download it unless there's a lot of tiny files instead of a bundle or two. What the article is complaining about doesn't seem like it's root cause of the slowness. When it comes to JS optimization in the browser there's usually a few great big smoking guns: 1. Tons of tiny files: Bundle them! Big bundle > zillions of lazy-loaded files. 2. Lots o…

>Do I understand why they're so much lower latency than REST calls on mobile networks? Not really: In theory, it's still a round-trip but for some reason an open connection can pass data through an order of magnitude (or more) lower latency on something like a 5G connection.

It's because a TLS handshake takes more than one roundtrip to complete. Keeping the connection open means the handshake needs to be done only once, instead of over and over again.

Re: Why Nextcloud feels slow to use

#114
post #9

For reference, 20 MB is three hundred and thirteen Commodores.

Sure, but what people leave out is that it’s mostly C and assembly. That just isn’t realistic anymore if you want a better developer experience that leads to faster feature rollout, better security, and better stabilty. This is like when people reminisce about the performance of windows 95 and its apps while forgetting about getting a blue screen of death every other hour.

Windows 2000 was quite snappy on my Pentium 150, and pretty rock solid. It was when I stopped being good at fixing computers because it just worked, so I didn't get much practice.

Re: Why Nextcloud feels slow to use

#115
post #83

Earlier quoted context omitted.

I recently needed to show a pdf file inside a div in my app. All i wanted was to show it and make it scrollable. The file comes from a fetch() with authorzation headers. I could not find a way to do this without pdf.js.

This made me try it once more and I got something to work with some Blobs, resource URLs, sanitazion and iframes. So I guess it is possible

Yeah, blobs seem like the right way to do it.

Re: Why Nextcloud feels slow to use

#116
post #80
post #38

Earlier quoted context omitted.

Recently people built a super-lightweigt alternative, named copyparty[0]. To me that looks like it does everything people tend to need without all the bloat. [0]: https://github.com/9001/copyparty

This is not an alternative as it only covers files. Mind what is in the article: "I like what Nextcloud offers with its feature set and how easily it replaces a bunch of services under one roof (files, calendar, contacts, notes, to-do lists, photos etc.), but ". For us Nextcloud AIO is the best thing under the sun. It works reasonably well for our small company (about 10 ppl) and saves us from Microsoft. I'm very gra…

Why should Germany be wasting public money on a private company who keeps shoveling more and more restrictions on their open-source-washed "community" offering, and whose "enterprise" pricing comes in at twice* the price MS365 does for fewer features, worse integration, and with added costs for hosting, storage, and maintenance?

* or same, if excluding nextcloud talk, but then missing a chat feature

Re: Why Nextcloud feels slow to use

#117

I don't think this article actually does a great job of explaining why Nextcloud feels slow. It shows lots of big numbers for MBs of Javascript being downloading, but how does that actually impact the user experience? Is the "slow" Nextcloud just sitting around waiting for these JS assets to load and parse? From my experience, this doesn't meaningfully impact performance. Performance problems come from "accidentally…

Agreed. Plus if it truly downloads all of that every time, something has gone wrong with caching. Overeager warming/precomputation of resources on page load (rather than on use) can be a culprit as well.

Relying on cache to cover up a 15MB JavaScript load is a serious crutch.

Re: Why Nextcloud feels slow to use

#119

The major shortcoming of NextCloud, in my opinion, is that that it's not able to do sync over LAN. Imagine wanting to synchronize 1TB+ of data and not being able to do so over a 1 Gbps+ local connection, when another local device has all the necessary data. There is some workaround involving "split DNS", but I haven't gotten around to it. Other than that, I thought NC was absolutely fantastic.

I had a similar issue with a public game server that required connecting through the WAN even if clients were local on the LAN. I considered split DNS (resolving the name differently depending on the source) but it was complicated for my setup. Instead I found a one-line solution on my OpenBSD router:

    pass in on $lan_if inet proto tcp to (egress) port 12345 rdr-to 192.168.1.10
It basically says "pass packets from the LAN interface towards the WAN (egress) on the game port and redirect the traffic to the local game server". The local client doesn't know anything happened, it just worked.

Re: Why Nextcloud feels slow to use

#120
post #16

Nextcloud not perfect but it's still one of a major project that has not shifted to business oriented licence and where all components are available and not paywalled with enterprise edition. So yes not perfect, bloated js but it works and is maintained. So I'd rather thanks all developers involved in nextcloud than whine about bloated js.

That's not quite right. There are features that are only available to enterprise customers, or require proprietary plug-ins like Sendent.

Do I need them for my home server? No. Do I need them for my company? Yes, but costs compared to MS 365 are negligible.

Post reply on HN