So far my experience with Nextcloud has been that it is a pain in the arse to install, and once it’s installed is slow as anything. Literally couldn’t run it on my pi 3b, now got it up and running pretty nicely on a NUC but it’s still not great. Have caching set up.

I have the notes app installed on my android phone and I can never used rich text editing because it gives timeout error.

This shouldn’t be this complicated. All I want is to de-Google my documents and notes, and self-host my kanban. I don’t really need the rest though it’s nice to have the options.

Do people use alternatives? Am I doing something completely wrong? I set it up using nginx which I know is not supported, but the alternative using Docker AIO didn’t allow me to use custom port easily.

  • @redcalcium
    link
    English
    2
    edit-2
    10 months ago

    It’s a PHP app inherited from owncloud so at some point you’ll just have to accept it won’t be as performant as apps written in compiled languages (and it also inherit owncloud’s quirks and other annoyance related to its php-based deployment). But this weakness is actually a strength too, being a php app makes extending its functionality very easy, resulting in a lot of community-developed plugins. Basically a trade-off between performance and features + community plugins availability. If you value performance more and don’t need anything beyond file sharing feature, there are plenty of other options right now.

    • AggressivelyPassive
      link
      fedilink
      English
      110 months ago

      I understand the history, and that may have been an excuse 6 months after the fork, but think about how long nc exists now. And how many features (like migrations) are apparently simply not worked on.

      NC is a great example of the current trend of “fuck good design, just throw more silicon at the problem”.

    • @thisisawayoflife@lemmy.world
      link
      fedilink
      English
      110 months ago

      I was thinking about this a couple of weeks ago. I’m running nextcloud in a VM - php recompiler, redis, mariadb, plenty of RAM (4GB). I’m spreading about 80GB of data across a few users, but it’s dog slow on mass upload. If I wanted to upload 1000 images from my phone, it would hours. I moved those photos to my laptop, which was fast, then tried uploading them to nextcloud via the Ubuntu desktop sync app, and it still took almost 2 hours. Nextcloud is backed by RAID6 storage and benchmarks suggest it’s over 300MB/sec write.

      I think it has something to do with file transfer overhead (start stop) similar to FTP impacting WebDAV, but that’s pure speculation on my part.

      I was wondering what it would take to rewrite Nextcloud core functionality in Java and use some kind of different interface than WebDAV, but I’ve got a lot of irons in the fire at the moment.

      • @redcalcium
        link
        English
        1
        edit-2
        10 months ago

        2 hours for uploading 1000 photos means it took 7.2s per photo upload. This is very slow, not sure if it’s just webdav overhead. Does uploading large files also slow (e.g. way below your raw network speed)?

        Could be related to this if you’re still on an older version: https://github.com/nextcloud/server/issues/33453

        • @thisisawayoflife@lemmy.world
          link
          fedilink
          English
          110 months ago

          LAN is gigabit, and I can sustain Gb speeds in regular file transfers via mounted nfs shares. There isn’t much difference over Wi-Fi (ubiquiti APs). Also running the latest Nc, 27.0.2.1 or whatever it is.