15 minutes ago, Nodiaque said:

First part is about the fact you said it's static, I simply say that mine is ondemand and that ondemand or dynamic won't change the problem with maximum children.

Second part is about the script. So that's why you got quoted

obviously the pm value reflects to the responsiveness. and the problem is max_children which is a static value for a upper max limit (which gets hit as seen from the comments). they just used the default value and never looked back.

the values are static, the pm value is also statically set, max_children is a static limit wether you run a host with 1 core and 1 disk and 1 container or 64 core with 64 disks and 64 containers, and so are most other values in unraid too.

another example is "disk utilization threshold (%)" which as a unit is completely irrelevantly scaled between a disk of 1TB and a disk of 24TB especially since they are defined as defaults, array disks content isn't allocated per data type, so depending on which disk the data happens to go there might or might not be enough space. Especially since "Minimum free space:" for shares is in turn defined as GB instead of % which in turn is also irrelevant since the shares size is dynamic where it one day could consist of x amount of disks and z amount another. you can't correlate between static units and dynamic units.

tldr; in the eyes of the customer / user the product doesn't work for a multitude of uderlying ignored factors. unraid doesn't scale, it could but they just don't realize it even though their definition of the product licensing is scaled. there doesn't even exist a document iterating any scalable considerations.

Edited December 15, 2025Dec 15 by Samsonight
typo

7.2.2 and this just showed up: (4 times in recent log) - RTX 3070 / Nvidia Driver Version: 580.119.02 / GPU statistics is present/enabled.

server reached max_children setting (50), consider raising it

Seems tied to JF playback.

Coincidentally (or not) was dealing with this issue just prior to:

NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x22:0x51:884)

This seemed to fix itself with a NVIDIA driver update and reboot.

Is there some underlying video card/vram/driver issue I am missing that has cropped up recently?

Edited December 19, 2025Dec 19 by goldbondx

This is happening to me as well with a fresh install of 7.2.3 with very minimal plugins/dockers on. Happens even when I stop all the dockers.

Intel quicksync driver, had GPU statistics but removed that and still happening.

FWIW I've narrowed at least my issue down a bit, was the unassigned devices plugin, or preclear or the other one when I had a gl.inet KVM plugged in.

Going to have to diagnose if it was the KVM or the actually plugins but the warnings seem to have dissapeared.

6 hours ago, Zervun said:

FWIW I've narrowed at least my issue down a bit, was the unassigned devices plugin, or preclear or the other one when I had a gl.inet KVM plugged in.

Going to have to diagnose if it was the KVM or the actually plugins but the warnings seem to have dissapeared.

I stand corrected, looks like it wasn't that...