# Remaining issues in NC 28.0.3 RC2

**URL:** <https://help.nextcloud.com/t/remaining-issues-in-nc-28-0-3-rc2/183289>\
**Category:** ℹ️ Support\
**Tags:** nc28\
**Created:** [February 24, 2024, 1:36pm UTC](https://help.nextcloud.com/t/remaining-issues-in-nc-28-0-3-rc2/183289 "2024-02-24T13:36:04Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![spyro](https://help.nextcloud.com/letter_avatar/spyro/32/5_5575768a8748004e209b776fc1b2916d.png) [@spyro](https://help.nextcloud.com/u/spyro)\
**Post date:** [February 24, 2024, 5:11pm UTC](https://help.nextcloud.com/t/remaining-issues-in-nc-28-0-3-rc2/183289/3 "2024-02-24T17:11:56Z")

</div>

No, there is not an “open github issue”. I’m one of literally _thousands_ of people who have brought this up (do a quick google for things such as “NC server is catastrophically / painfully / astonishingly / infeasibly slow” and you’ll find no shortage of people complaining that even over a LAN, and with no WAN at all, Xfer speeds are in the toilet.

I’m not opening a “github issue” either. “Open a github issue” is (and has been in my entire 35 years of OSS experience) code for “Please go away”. People who really want to deal with a users issue will either:

1. Work out that it’s a prexisting problem and point them at a “github issue” that they’ve already created to help users out .
2. Work out that this is a new problem, and work with the user to explore / document the issue, eventually either developing a fix or workaround, which can then be documented by opening an issue.

Theres no issue for Federation, either, because I havent opened one. I came to the forums to talk to people and ask questions. I do my best to also impart what knowledge I do have (you can easily see I’ve been helping others), and I do my best to not ask questions that have already been answered.

I’ve been here 8 days, and I’ve read over 400 posts, and made 30 odd.

I’m smart enough (and been doing IT stuff long enough) that I can see when I’ve done all the proper steps, only to find that it doesn’t work and that the reason is undocumented.

Thats _WHY_ Ive come to ask for help here.

I’ve another thread re: federation - its here:

> [@Nextcloud works except LARGE federated shares. cURL 500 errors in log](https://help.nextcloud.com/t/nextcloud-works-except-large-federated-shares-curl-500-errors-in-log/181968/10):
>
> oh and I renamed the test file to remove the spaces and special characters at some point (no change though, still failed)

And another re: the photo app DOS - read here:

> [@Photo viewing cripples server](https://help.nextcloud.com/t/photo-viewing-cripples-server/182064):
>
> Hi, Is it an intended feature of NC28 that scrolling through the photos app in the web interface is an effective DoS against every other simultaneous operatoin on a 4 core 2GHz x86 with 8GB of RAM and RAID5 that can hit 600MB/s? I can’t believe that a machine with that much horsepower (even though you can spend far more on hardware nowadays) is really incapable of serving up a few thumbnails over the LAN without completely crippling itself. I honestly thought that nextclouds utterly tragic up…

Until last night, preview concurrency was “whatever the default is” because I had assumed that the devs would select sensible defaults - either “not much”, or some heuristic, like “CPU cores -1 or 1 at minimum” or “cores/2 rounded up”, rather than the completely insane “infinity” which is the default.

I also had no idea there was an option for changing it until last night. No-one else has mentioned it to me until now, after I already found it.

Its certainly not mentioned in the setup guide, which is where it should be, since the defaults are insane, and guaranteed to DOS anything but a tricked-out gaming rig…

I am referring to the built in preview generator, although I’ve disabled that now and am using preview-generator.

If you select (as I’ve done) a max size preview of 256x256, then when you go to ACTUALLY look at your photos (ie. not just previews thumbnails), they look like total sh\*t, because you get a scaled up 256 x “whatever” image, not the actual original.

Why? If I click on the thumbnail image, I WANT THE ORIGINAL (like anyone else would).

What this means is that I can either cripple my machine (ie. let the preview generator generate unlimited previews up to the 4K (!) defaults), because all my pictures are \<4K, and so at least I’m guaranteed to always see them in full quality when I open them,

or I can run the preview-generator app (yes, I know its not in the base install) and have useable speed scrolling in Photos, etc., but then I can never see the images in full quality in the “Memories” app. (which I have to use, because “Photos” is so utterly CR\*P that its useless in every way - Slow, hard to use, DoSes your server etc.)

What I _want_ is for previews to never be \>256x256, but for apps to ALWAYS open the original image when I click in the previews. Not just the “largest preview”, which is uselessly small for fullscreen display.

I can’t believe anyone capable of coding actually took the extra time it must take to screw this up. The rules are really simple -

1. If rendering a thumbnail, select the closest size that matches or exceeds the size you want,or if \> the largest thumbnail, simply use the original).
2. If rendering the main image, ie. NOT rendering a thumbnail, then use the original image.

I mean, seriously - if it has to generate a 100% resolution thumbnail in order for the f\*cking photos app to display a clean image, that really is insane. The image is _already there on disk_. WTF. Why is NC wasting my disk duplicating the original image?

---

_[View the full topic](https://help.nextcloud.com/t/remaining-issues-in-nc-28-0-3-rc2/183289)._