Remaining issues in NC 28.0.3 RC2

Ah.

To be fair I don’t use the stock database anyway. I use postgresql 17.

It sometimes happens that NC is covering an LTS, temporarily. Not the same

I’m finding Trixie to be a good choice for the rockpro64 (with the kernel from experimental. I’m doing a writeup on configuring it from scratch, with u-boot, grub, etc. No SD card needed, boots direct from a SSD on SATA with a 9TiB RAID on spinning rust. Total power consumption is low enough that my energy meter is having trouble measuring it. Estimate over 3 hours indicates it’s drawing something like about 30W including the discs. Peak was ~70W but brief.

Performance is decent for my purposes, getting ~80MB/s average from the array. The SSD manages ~350MB/s (it’s max).

Getting NC not to eat all the RAM has been the challenge. Limiting php-fpm to 4 instances (static) has really helped, as does enabling the php and postgresql jit (and lowering its cost values from the default.

It’s been stable now for about 10 days. Finally. (To be clear - Debian was always stable on this hardware, NC has been the troublemaker.

Biggest thing I want to do now is limit the max client request size to something reasonable (512MB is not reasonable). I really hope the NC31 changes to chunking uploads solves this. (I can limit the request size to 5MiB now, and the Linux desktop client can be kicked into line on this, but the web uploads and Android client break (because there seems to be no way to configure them to use sane vaues). Here’s hoping…) This would really help because otherwise large transfers consume all the available resources. Increasing the number of php-fpm instances doesn’t really help - the machine just grinds to a halt handling them and runs out of memory.

You can do that (at least with Ubuntu, and mostly also with Debian), as long as you upgrade your OS every two years to the latest (LTS) release.

It’s just not practical for a software like Nextcloud to support 5 or even ten years old PHP versions. I mean this not just about security, which I guess those distros do a reasonably good job when backporting security fixes to older versions, but also about making use of performance improvements and new features, that were introduced in newer versions of PHP.

Use the Sury repos. Ondrej Sury is an official maintainer of PHP in the Debian project, and he knows what he’s doing, so it’s not just some random third-party repo that’s going to create a Franken-Debian that Debian purists are always trying to scare you about.

Exactly my kind of humour. Telling stories about sysadmins who only want to use official stable packages from an (LTS) distro, while using Debain testing with an experimental kernel on some tinkering board :wink:

And one more thing:

I don’t think debates like this in the forum, especially when different topics are getting mixed up and/or people think they are entitled to have the software tailored exactly to their specific needs, are particularly helpful to anyone, and I highly doubt that Nextcloud will fundamentally change their strategy tomorrow because of such a thread :person_shrugging:

I never said I was using deb stable - just that I use Debian and like to use the packaged tools, rather than someone elses giant blob.

I’m sure Pine64 would love to hear your description of their hardware. Why don’t you email them?

I support the other poster on here in their desire to run LTS and their reasons. I was posting in solidarity.

Unfortunately, Debian on Rockpro64 isn’t stable without newer packages (mostly the kernel TBF), so needs must.

Thank you for your condescending ‘helpful’ suggestion.

Of course I’m using Sury already, but the issue is that NC chases ‘new, shiny’ at the expense of ‘reliable, tested’.

Your point scoring approach does not address this issue in any meaningful way.

1 Like

Hear hear.

Without details about which bugs people are talking of, we couldn’t even create a list of the 10 bugs that are most annoying/problematic for the community. The bugs on github receiving the most reactions:

don’t seem to be very representative.

As community, when testing new versions we could focus on such points, so they get more visibility. Especially since we don’t know in advance which new and shiny features will be in the new version, at least we test something reasonable.

1 Like

Let’s break the original post down:

What does slow performance mean? I get aboud 80 to 90 MBs/sec from my PC over a 1Gig connection, which I find reasonably fast for a WebDAV connection.

What exactley does ‘does not work’ mean?

Sorry, maybe you can put that phrase in a ticket in your company, or start a call with that phrase on a support hotline where someone on the other end is being paid to work things out with you, but in a community support forum this is an absolute no go imho.

Oh, and btw, even on a professional support hotline, undifferentiated error descriptions like that are unproductive and a waste of time for everyone involved.

Not an issue I’m expiriencing.

Well again, What does that even mean? I find them pretty useful.

1 Like

Why? That post is ancient now I literally gave up on NC until about 30.0.1 in the mean time. What do you want to bring this up for now, other than to distract from the more recent issues? Or do you just love a good argument?

As I mentioned back then before february, it means ~5-6MB/s

In fairness, the NC30 build is behaving rather better in this regard. GoK why, but I’ll take it.

I wasn’t giving a bug report - I was annoyed and reporting on all the points I’d noted that hadn’t been fixed for a lot of users (use google) for a long time. I made plenty of reports on these forums of the actual problems in other posts, but you’re choosing to pick on this one where it got summarised.

Anyhow - NC30.0.3 seems to have working federation. no idea what changed, or if it’ll stay working, but it certainly wasn’t my router config, which hasn’t changed. In 28, it refused to ever “greenlight” one of the servers, and when it did anything at all, it tended to work intermittently. No explanations of what the green light was for was ever forthcoming.

This wasn’t a support ticket, it was a rant, as well you know.

I’d raised the issues over and over in the forum to try to get any kind of support (the forum IS titled “support” after all), but all I ever got was confused answers from other users. Never once did a dev step in to help.

A professional support forum this most certainly ain’t.

Lucky you. It was caused by the idiotic defaults in that version.

What it meant was that preview generation would basically cripple the machine. It’s small and not particularly powerful. NC basically assumes it has all the horsepower and RAM in the world. The preview generator (back then) simply would not respect any reasonable limits on CPU time. It consumed all the resources of the machine, and the UI would grind to a halt.

At the time, I worked around it with offline preview generation (not without it’s issues at the time). It’s quite a bit better now (but still has daft defaults).

Anyhow, I don’t see how dredging up an ancient post is helping anyone. What are you trying to prove here?

Btw - did you ever think that some of us don’t want Github accounts? You do know who owns it now, right?

I don’t have time to respond to your post ind detail right now, so just this much…

I think that megathreads, or whatever you want to call this thread, where all kinds of problems are thrown together wildly, don’t get us anywhere, but only specific bug reports on GitHub, and yes, sometimes they don’t get fixed immediately, and sometimes never, especially when it comes to more fundamental things like where the project as a hole should go.

Ultimately, Nextcloud’s ambition is best described as being a replacement for Google Workspace and M365, and that’s where the priorities lie.

With that in mind, It will probably never be a 1:1 replacement for NFS or SMB shares, it will never be Syncthing + fancy WebUI, it will probably never be a 100% replacement for Google Photos, it will probably never be a replacement for a dedicated document management solution, the list goes on and on. Take a look at Google Workspace and you’ll see where we are heading,

And then there are the apps (iOS, Android, desktop), which is another thing that people keep getting upset about. Again, compare it to Google Workspace (and no, Google Photos, or mobile two way sync/backup, or backup for desktops is not part of Google Workspace)

By the way, my girlfriend has to use the Google desktop client on a Macbook for her work. Just this much: Things don’t always go smoothly there either, especially if you’re not running the latest version of macOS.

If we are talking purely about download speed, here is a hint for nginx configurations: http2 can severely limit download speed. If you disable it speeds can massively jump.

Ok. Are you a NC dev though? I mean, why are you answering for them?

You’ve made that abundantly clear many times.

So the only way to collaborate is via a Microsoft owned platform?

What’s the point of these forums then?!

[quote] and yes, sometimes they don’t get fixed immediately, and sometimes never, especially when it comes to more fundamental things like where the project as a hole should go.
[/quote]

Well, that’s pretty bad. Fixing very obvious bugs should ALWAYS be done in a reasonable time.

Don’t you think that the CALENDAR app is kind of critically important, then?

Gotcha. “Copy, don’t innovate”. Well, that’s a shame.

“Which people keep getting upset about”? Do you realise how offensive that is?

People are “upset” about the apps because they are inconsistent, and, frankly, cr^W rubbish. I just found ANOTHER bug in the Android sync client just today (it’ll upload partial files if you dont exclude hidden files and select the delete after upload option).

Compared to the polish of the Google and M$ offerings, NC is lagging WAAAAAAY behind. Having consistent apps for sync should be a fundamental basic thing, and it seems like everyone except the NC devs can see this.

I’m sure Google would love her to put a report in their Github.

(See, that’s meant to be the difference - OSS projects are supposed to listen to their users and interact, unlike Google et.al., who are expected to ignore them. That’s why everyone is annoyed with NC devs - they aren’t visible in the community.)

PS. See you at FOSDEM…

Hello @spyro,

you use this forum to complain about various topics and show almost no constructiveness to solve issues.
Endless threads in a support category help no one.
This is a user forum where people help each other and not insult people. “Jerk” is such an insult (I flagged your post before you rewrote it).

I hereby give you an official warning and will mute you for a week (aligned with the mod crew).

Please think about your attitude during this time.
If you respect the forum rules and need help, you are welcome again.

cu,
rakekniven

1 Like

I’m closing here, as this topic has no real goal and even reopening the original topics did not lead to success.