I want to add this parameter "--o:per_document.max_concurrency=2" in the Yaml file How do I do that?

ℹ️ Support
, , , ,
1
Support intro

Sorry to hear you’re facing problems. :slightly_frowning_face:

The community help forum (help.nextcloud.com) is for home and non-enterprise users. Support is provided by other community members on a best effort / “as available” basis. All of those responding are volunteering their time to help you.

If you’re using Nextcloud in a business/critical setting, paid and SLA-based support services can be accessed via portal.nextcloud.com where Nextcloud engineers can help ensure your business keeps running smoothly.

Getting help

In order to help you as efficiently (and quickly!) as possible, please fill in as much of the below requested information as you can.

Before clicking submit: Please check if your query is already addressed via the following resources:

(Utilizing these existing resources is typically faster. It also helps reduce the load on our generous volunteers while elevating the signal to noise ratio of the forums otherwise arising from the same queries being posted repeatedly).

I finally got nextcloud installed on my synology NAS and it works for 99%. One thing bugs me tough. My NAS has a processor with only two cores and when I open a document I get a reminder that I need to change my processor count.

I am just a user and not a software engineer and none of the instructions helped me to solve this problem. I know what I have to do, but not how to do it.

The instructions I read are also very unsafe. I think things like processor concurrency should be set at installation and be determand in this procedure. If this can’t be done you should be able to set it in the yaml file.

Has anyone an idea how to do this?

2

It would be helpful if you provided more context. Nextcloud is a large system. There is a support template for a reason. :wink:

3

Dear Josh,

Thanks for your reaction. I delibrately did not fill in the form because in my expirience too much information distracts from the issue at hand.

But hereby some extra information:

I installed the latest version of nextcloud-aio (30.0.8.1) on a DS218+ synology NAS in a docker container. The NAS has 8Gb of memory.

This is the cpu info:

Taak: cpu info
Starttijd: Sat, 13 Sep 2025 13:21:44 +0200
Stoptijd: Sat, 13 Sep 2025 13:21:44 +0200
Huidige status: 0 (Normaal)
Standaard output/fout:

processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 92
model name	: Intel(R) Celeron(R) CPU J3355 @ 2.00GHz
stepping	: 9
microcode	: 0x3c
cpu MHz		: 2001.000
cache size	: 1024 KB
physical id	: 0
siblings	: 2
core id		: 0
cpu cores	: 2
apicid		: 0
initial apicid	: 0
fpu		: yes
fpu_exception	: yes
cpuid level	: 21
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 ds_cpl vmx est tm2 ssse3 sdbg cx16 xtpr pdcm sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave rdrand lahf_lm 3dnowprefetch intel_pt ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust smep erms mpx rdseed smap clflushopt sha_ni xsaveopt xsavec xgetbv1 dtherm ida arat pln pts md_clear arch_capabilities
bugs		: spectre_v1 spectre_v2
bogomips	: 3993.43
clflush size	: 64
cache_alignment	: 64
address sizes	: 39 bits physical, 48 bits virtual
power management:

processor	: 1
vendor_id	: GenuineIntel
cpu family	: 6
model		: 92
model name	: Intel(R) Celeron(R) CPU J3355 @ 2.00GHz
stepping	: 9
microcode	: 0x3c
cpu MHz		: 2001.000
cache size	: 1024 KB
physical id	: 0
siblings	: 2
core id		: 2
cpu cores	: 2
apicid		: 4
initial apicid	: 4
fpu		: yes
fpu_exception	: yes
cpuid level	: 21
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 ds_cpl vmx est tm2 ssse3 sdbg cx16 xtpr pdcm sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave rdrand lahf_lm 3dnowprefetch intel_pt ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust smep erms mpx rdseed smap clflushopt sha_ni xsaveopt xsavec xgetbv1 dtherm ida arat pln pts md_clear arch_capabilities
bugs		: spectre_v1 spectre_v2
bogomips	: 3993.43
clflush size	: 64
cache_alignment	: 64
address sizes	: 39 bits physical, 48 bits virtual
power management:

The warning I get is this:

Schermafdruk van 2025-09-13 13-33-45
Schermafdruk van 2025-09-13 13-33-454434×2862 821 KB

The default processor count of nextcloud aio is 4. My machine has 2. So I would like to change that. I already found out I have te change a file coolwsd.xml, but that is at best a workaround and no solution. (apart from the fact that I can´t find the file and don´t know how to change it)

My question is: Is there a command I can enter in the yaml file where is can set this parameter. Something like the parameter “COLLABORA_SECCOMP_DISABLED: true” I had to add to get my collabora to function.

Here you can find my compose.yaml: Access via Synology

Kind regards

Marcel Reijnen

4

You should be able to specify any Collabora -o options under Additional Collabora options in the Optional.Containers AIO config area.

1 Like
5

Thank you for this information. That is helpfull.

I tried adding the line –o:per_document.max_concurrency=2 In the field for the extra options. It had no effect so I asume I am doing something wrong here.

Can you help me with this line?

6

Hey, I have the same problem. Adding the option to “Additional Collabora options” did not fix it. Have you found a solution?

7

Your Celeron J3355 is a low-end, power-efficient CPU, adequate for simple tasks, but not a performance machine.
Compared to modern CPUs, it is quite weak. Performance is closer to a mid-range smartphone SoC from ~2017 or an old Intel Core 2 Duo, fine for lightweight server tasks (NAS, Pi-hole, small database, basic web browsing) but it’s not suitable for more heavy computation like Collabora Online.

There’s nothing you can do about it. The “warning” is a message telling you that your server’s performance is simply too weak for a high-performance Collabora Online Server. You can’t simply solve this by increasing the number of virtual processors as you’re imagining. For that, you need a more powerful server, meaning truly more powerful hardware. It’s a miracle that your AIO even works on such weak hardware and that documents can even be opened and edited in Nextcloud Office!
On the other hand, you have the advantage of an extremely low power consumption of 10W!
You can simply dismiss the message as information if everything still works for your purposes, but truly high-performance tasks, where multiple users work simultaneously on the Collabora Online Server, aren’t possible. The hardware is simply not sufficient for that.

h.t.h.

ernolf

2 Likes
8

The setting we are talking about (per_document.max_concurrency) determines how many threads can be used when accessing and processing files. If the system has less logical threads than the given number the warning is shown. We just want to tell Collabora that there are less than 4 threads available, but Nextcloud AIO seemingly does not pass the argument over to the Collabora docker instance it creates.

If you decrease the number, performance will suffer I guess, but in my case at least this does not matter as only I will be using my Collabora instance, so no concurrent file access by multiple people. Even one single thread would probably be enough for my use case.

Also, nobody in this thread was talking about increasing the number of virtual processors…

1 Like
9

I’m afraid I have to disappoint you:
Even if you set

num_prespawn_children 1

(which, unlike the manual, defaults to 4 and not 1) and

per_document.max_concurrency 1

you will still get the warning.

This warning will only disappear once you have at least 4 actual hardware cores.

I’m sorry I mistook it that way. I just know that this message always appears when there are fewer than four cores and I thought you did know that as well. and was trying to solve it with virtual cores.

Read this please:

ernolf

2 Likes
10

Thanks for your clarification. I know my server is weak. It is a compliment to the developers of nextcloud that it even works on this hardware. It takes some time to open a document in collabora, but when you’re in it works like a charm, even with four people simultanously.

A talk session with four people works also reasonably well if people don’t move to much.

1 Like
11

This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.