Closed muellerm01 closed 2 years ago
Hi, thanks for your report. I fear though that there is not much we can do here because we install everything based on the docs.
Feel free to read the following docs though: https://github.com/nextcloud/spreed#how-to-have-the-maximum-number-of-participants-in-a-call
Also it seems like your cpu is pretty limitied. Feel free to try to increase the cpu count
OK, sorry I thought HPB was part of AIO because it is configured. I requested your sales team but think the minimum user count is around 100 to get enterpise support and search for a solution below that. Let´s see what i will get from them.
I also tried it with a larger CPU, but that doesn't seem to change anything.
I think in the range of 50 participants and an on premise installation. But I could not find a purchasable solution so far.
Hosting is not an option for me. Then I could just take teams.
OK, sorry I thought HPB was part of AIO because it is configured.
yes, the HPB is part of AIO.
It seems like it is just not scaling as good as promised...
But than HPB with a limit of 7-8 thems to be confusing.
But than HPB with a limit of 7-8 thems to be confusing.
yes, it is
Is something configured incorrectly?
Noth that I am aware of.
You can have a look yourself: https://github.com/nextcloud/all-in-one/blob/main/Containers/talk/start.sh
Maybe this is the problem for you? https://github.com/nextcloud/all-in-one/blob/8fedcb48109a62e794eb4ae6a5ae258ae43c4ef8/Containers/talk/start.sh#L55
feel free to adjust that number in the container and try again.
I looked, but I only know the documentation from others and not what is recommended.
Hm ok good point, I'll try that.
Feel free to report back if adjusting this number makes it work.
We can then adjust the number if it works for you.
I'll reopen this until then :)
Or lets go the other way around. I'll increase the value and you can test it with the next release.
I tryed docker stop
But nothing changed, the limit is still between 7 and 8
the janus log looks like a crash loop but hard to read
What is the output of cat /etc/signaling/server.conf
after a restart?
the janus log looks like a crash loop but hard to read
Interesting! Can you share the logs?
connectionsperhost = 40
connectionsperhost = 40
Hm...
I also tryed to disconnect user 7 and 8 and than reconnect again 8 before 7 the last user is always the one with the problem
I also tryed to disconnect user 7 and 8 and than reconnect again 8 before 7 the last user is always the one with the problem
So there seems to be a hard limit at 7-8 somehow...
Hm I have a HPB running with these sources and docker-compose, it looks like this is not limited to 7-8
Hm I have a HPB running with these sources and docker-compose, it looks like this is not limited to 7-8
So then it is probably a configuration issue, right.
I used this guide for configuration https://markus-blog.de/index.php/2020/07/30/how-to-install-nextcloud-talk-high-performance-backend-with-stun-turnserver-on-ubuntu/
Thanks! At first glance it looks comparable. I'll adjust our config to match this guide a bit better.
thx but can´t say what is different hm everything is splitted in 4 container
Hey, I just published a new talk container. Feel free to try that one out and please report back if it is now better than before. :)
Hm, has not changed the behavior.
Hm...
How to use GitHub
Steps to reproduce
Software Install Nextcloud AIO 0.8 like documented
Hardware: Azure North Europe Standard D4as v4 (2 vcpus, 8 GiB Arbeitsspeicher) 8 Gbit download (measured) 1,8 Gbit upload (measured)
Steps:
Expected behaviour
Nextcloud talk participant limit should be releated to CPU, RAM and upload/download speed
Actual behaviour
CPU runs on 0,5 cores RAM 2,5 GB used Upload/Download ~20Mbit and participant limit is between 7 and 8
Nextcloud AIO version
AIO 0.8
Current channel
latest channel
Other valuable info