Help us test build of 2.2.31 (looking to improve performance in mogodb)

[Fred Dixon]

Hi everyone,

We're working on 2.2.31 (currently in development) which includes some work on improving the performance of mongodb (and hence the overall scalability of BigBlueButton).  

The current build of 2.2.31 has the following pull request.

  Remove callback functions from mongo operations in order to execute them synchronously.

  - https://github.com/bigbluebutton/bigbluebutton/pull/10902

We're looking for a few adventurous admins to test this under load.  If you can, let us know if you see any improvements (or regressions).

To try out this pre-release of 2.2.31, you can switch a (non-production) BigBlueButton server to use the latest build packages by running the following command

echo "deb https://ubuntu.bigbluebutton.org/xenial-220-dev22a bigbluebutton-xenial main" | sudo tee /etc/apt/sources.list.d/bigbluebutton.list

and then update the server to the latest packages using either using the docs at

   https://docs.bigbluebutton.org/2.2/install.html#upgrading-from-bigbluebutton-22

or using bbb-install.sh with the following parameter

  -v  xenial-220-dev22a

After upgrading, `sudo bbb-conf --check` should show build 2.2.31.   

Regards,... Fred

-- 

BigBlueButton Developer

http://bigbluebutton.org/

Like BigBlueButton?  Tweet us at @bigbluebutton

[Luiz Gonzaga da Mata]

H, Fred,

I can install it in the homologation environment, but it would basically test the upgrade process and basic functionality tests.

There is no charge in it. This is enough?

Regards, ... Luiz Gonzaga.

--
You received this message because you are subscribed to the Google Groups "BigBlueButton-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bigbluebutton-dev/CAOeuy5NRpe3tx1JSxOfa%2BkOUG8Rg3Cb4dGGoi3C0kuuduvp2kg%40mail.gmail.com.

[Fred Dixon]

Hi Luiz,

We're pretty sure the upgrade process works -- let us know if you find anything.

It's running it under load that we're looking for help in testing.

Regards,... Fred

To view this discussion on the web visit https://groups.google.com/d/msgid/bigbluebutton-dev/CAESey_pp_9T-gAcUbmKyxC-go9jM9WpW5Zdpkugmt_FbF3EG-w%40mail.gmail.com.

[Luiz Gonzaga da Mata]

Hi Fred,

the installation and upgrade is oK.

Bellow, somethings of my environment after the upgrade.

A) 4 processors in my server:

cat /proc/cpuinfo|grep processor|wc -l
4

B) 1 running process of mongodb:

ps -ef|grep mongodb
mongodb   7138     1  0 20:02 ?        00:00:22 /usr/bin/mongod --config /usr/share/meteor/bundle/mongo-ramdisk.conf --oplogSize 8 --replSet rs0 --noauth --nojournal

C) 70 threads of process 7138

ps -eLf |grep 7138|grep -v grep|wc -l
70

root@webconferenciads02:/dados/greenlight# ps -eLf |grep 7138|grep -v grep
mongodb   7138     1  7138  0   70 20:02 ?        00:00:00 /usr/bin/mongod --config /usr/share/meteor/bundle/mongo-ramdisk.conf --oplogSize 8 --replSet rs0 --noauth --nojournal
mongodb   7138     1  7176  0   70 20:02 ?        00:00:00 /usr/bin/mongod --config /usr/share/meteor/bundle/mongo-ramdisk.conf --oplogSize 8 --replSet rs0 --noauth --nojournal
mongodb   7138     1  7177  0   70 20:02 ?        00:00:00 /usr/bin/mongod --config /usr/share/meteor/bundle/mongo-ramdisk.conf --oplogSize 8 --replSet rs0 --noauth --nojournal
mongodb   7138     1  7179  0   70 20:02 ?        00:00:00 /usr/bin/mongod --config /usr/share/meteor/bundle/mongo-ramdisk.conf --oplogSize 8 --replSet rs0 --noauth --nojournal

<snip>

mongodb   7138     1  7737  0   70 20:02 ?        00:00:02 /usr/bin/mongod --config /usr/share/meteor/bundle/mongo-ramdisk.conf --oplogSize 8 --replSet rs0 --noauth --nojournal
mongodb   7138     1  7738  0   70 20:02 ?        00:00:00 /usr/bin/mongod --config /usr/share/meteor/bundle/mongo-ramdisk.conf --oplogSize 8 --replSet rs0 --noauth --nojournal
mongodb   7138     1  9665  0   70 20:17 ?        00:00:00 /usr/bin/mongod --config /usr/share/meteor/bundle/mongo-ramdisk.conf --oplogSize 8 --replSet rs0 --noauth --nojournal
mongodb   7138     1  9666  0   70 20:17 ?        00:00:00 /usr/bin/mongod --config /usr/share/meteor/bundle/mongo-ramdisk.conf --oplogSize 8 --replSet rs0 --noauth --nojournal
mongodb   7138     1  9667  0   70 20:17 ?        00:00:00 /usr/bin/mongod --config /usr/share/meteor/bundle/mongo-ramdisk.conf --oplogSize 8 --replSet rs0 --noauth --nojournal
mongodb   7138     1  9668  0   70 20:17 ?        00:00:00 /usr/bin/mongod --config /usr/share/meteor/bundle/mongo-ramdisk.conf --oplogSize 8 --replSet rs0 --noauth --nojournal
root@webconferenciads02:/dados/greenlight# 

D) Thread of Storage:

cat /var/log/mongodb/mongod.log|grep thread|grep -v thread1

2020-11-29T20:02:38.881-0300 I STORAGE  [initandlisten] wiredtiger_open config: create,cache_size=7507M,session_max=20000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=none),file_manager=(close_idle_time=100000),checkpoint=(wait=60,log_size=2GB),statistics_log=(wait=0),verbose=(recovery_progress),,log=(enabled=false),

E) Version in log of Mongodb:

2020-11-29T20:02:38.849-0300 I CONTROL  [initandlisten] db version v3.4.24
2020-11-29T20:02:38.849-0300 I CONTROL  [initandlisten] git version: 865b4f6a96d0f5425e39a18337105f33e8db504d

F) 10 users In BBB and 7 sockets TCP in mongodb.

lsof -p 7138|grep TCP|grep -v LISTEN
mongod  7138 mongodb   21u  IPv4           15276956      0t0      TCP 127.0.1.1:27017->localhost:38502 (ESTABLISHED)
mongod  7138 mongodb   30u  IPv4           15276957      0t0      TCP 127.0.1.1:27017->localhost:38504 (ESTABLISHED)
mongod  7138 mongodb   31u  IPv4           15276958      0t0      TCP 127.0.1.1:27017->localhost:38506 (ESTABLISHED)
mongod  7138 mongodb   89u  IPv4           15349997      0t0      TCP 127.0.1.1:27017->localhost:38896 (ESTABLISHED)
mongod  7138 mongodb   90u  IPv4           15349998      0t0      TCP 127.0.1.1:27017->localhost:38898 (ESTABLISHED)
mongod  7138 mongodb   91u  IPv4           15349999      0t0      TCP 127.0.1.1:27017->localhost:38900 (ESTABLISHED)
mongod  7138 mongodb   92u  IPv4           15350000      0t0      TCP 127.0.1.1:27017->localhost:38902 (ESTABLISHED)

root@webconferenciads02:/dados/greenlight# lsof -p 7138|grep TCP|grep -v LISTEN|wc -l
7

G) Only 1 thread used in log of mongodb and 8 connections.

2020-11-29T20:02:45.017-0300 I NETWORK  [thread1] connection accepted from 127.0.0.1:38502 #5 (1 connection now open)
2020-11-29T20:02:45.087-0300 I NETWORK  [thread1] connection accepted from 127.0.0.1:38504 #6 (2 connections now open)
2020-11-29T20:02:45.090-0300 I NETWORK  [thread1] connection accepted from 127.0.0.1:38506 #7 (3 connections now open)
2020-11-29T20:17:01.817-0300 I NETWORK  [thread1] connection accepted from 127.0.0.1:38812 #8 (4 connections now open)
2020-11-29T20:17:05.522-0300 I NETWORK  [thread1] connection accepted from 127.0.0.1:38896 #9 (4 connections now open)
2020-11-29T20:17:05.551-0300 I NETWORK  [thread1] connection accepted from 127.0.0.1:38898 #10 (5 connections now open)
2020-11-29T20:17:05.567-0300 I NETWORK  [thread1] connection accepted from 127.0.0.1:38900 #11 (6 connections now open)
2020-11-29T20:17:05.573-0300 I NETWORK  [thread1] connection accepted from 127.0.0.1:38902 #12 (7 connections now open)
2020-11-29T21:17:01.172-0300 I NETWORK  [thread1] connection accepted from 127.0.0.1:40420 #13 (8 connections now open)

It can be useful for your evaluation.

If I put version 2.2.31 into production negotiated with the user and I notice a problem, is there a way to quickly revert this implementation like the 3 Kurento servers to 1 in a restart?

Regards, ... Luiz Gonzaga

To view this discussion on the web visit https://groups.google.com/d/msgid/bigbluebutton-dev/CAOeuy5Pp8Vi_K-B_4-Xfk-fF20GS_xKw-K0_tTWEpAYA592PEQ%40mail.gmail.com.

[Luiz Gonzaga da Mata]

Hi Fred,

I understand that the problem is in the use of Mongodb in Meteor uniprocessor and not in the BBB code.

Experts can help us with this assessment.

Why did I pass this data on Mongodb in the Meteor X Mongodb package?

There is no sense in a process with 70 threads running within 1 process allocated on 1 processor. It is not scalable.

I installed https://www.percona.com/doc/percona-server-for-mongodb/4.2/install/apt.html

The mongodb 3.4 has been removed and this percona-server-mongodb-server 4.2 (default in memory) is working.

The BBB too and without any adjustment to it!

root@ubuntu01:/var/lib/mongodb# bbb-conf --status
nginx —————————————————► [✔ - active]
freeswitch ————————————► [✔ - active]
redis-server ——————————► [✔ - active]
bbb-apps-akka —————————► [✔ - active]
bbb-transcode-akka ————► [✔ - active]
bbb-fsesl-akka ————————► [✔ - active]
red5 ——————————————————► [✔ - active]
tomcat7 ———————————————► [✔ - active]
mongod ————————————————► [✔ - active]
bbb-html5 —————————————► [✔ - active]
bbb-webrtc-sfu ————————► [✔ - active]
kurento-media-server ——► [✔ - active]
etherpad ——————————————► [✔ - active]
bbb-web ———————————————► [✔ - active]

root@ubuntu01:/var/lib/mongodb# mongod --version
db version v4.2.5-5
git version: 3e9770ff28bc8e5b7b663da9504effb71c973b85
OpenSSL version: OpenSSL 1.0.2g  1 Mar 2016
allocator: tcmalloc
modules: none
build environment:
    distarch: x86_64
    target_arch: x86_64

aptitude search mongodb

p   mongodb                         - object/document-oriented database (metapac
p   mongodb:i386                    - object/document-oriented database (metapac
p   mongodb-clients                 - object/document-oriented database (client
p   mongodb-clients:i386            - object/document-oriented database (client
c   mongodb-org                     - MongoDB open source document-oriented data
p   mongodb-org-mongos              - MongoDB sharded cluster query router      
c   mongodb-org-server              - MongoDB database server                  
p   mongodb-org-shell               - MongoDB shell client                      
p   mongodb-org-tools               - MongoDB tools                            
p   mongodb-server                  - object/document-oriented database (server
p   mongodb-server:i386             - object/document-oriented database (server
p   percona-backup-mongodb          - Percona Backup for MongoDB is a distribute
p   percona-server-mongodb          - This metapackage will install the mongo sh
p   percona-server-mongodb-dbg      - Debugging package for Percona Server for M
p   percona-server-mongodb-mongos   - This package contains mongos - the Percona
i   percona-server-mongodb-server   - This package contains the Percona Server f
i A percona-server-mongodb-shell    - This package contains the Percona Server f
p   percona-server-mongodb-tools    - Mongo tools for high-performance MongoDB

Regards.

[Fred Dixon]

Hi Luiz,

What is the Percona Server?  Does it help scale BigBlueButton?

Regards,... Fred

To view this discussion on the web visit https://groups.google.com/d/msgid/bigbluebutton-dev/CAESey_p-X63xebUHUdXTOQPQPhoPH_3bNQFX4YArt3MKmTVi3g%40mail.gmail.com.

[Luiz Gonzaga da Mata]

Hi Fred,

more than the evolution from versions 3.x onwards, it allows bug fixes and BBB performance and evolution in addition to Ubuntu packages.

"Expand that power with Percona Server for MongoDB, a free, open source drop-in replacement for MongoDB Community Edition but with enterprise-grade functionality.

Percona Server for MongoDB delivers high-performance and reliability to enterprises looking to achieve optimum performance, without being tied into an expensive proprietary software vendor relationship."

https://www.percona.com/software/mongodb/percona-server-for-mongodb

Regards,

To view this discussion on the web visit https://groups.google.com/d/msgid/bigbluebutton-dev/CAOeuy5NMk_kQYTTc7vS%3DTOEYzQjWLnwb7V9m-1oXH6HOm4LnOg%40mail.gmail.com.

[Luiz Gonzaga da Mata]

Hi Fred,

here you can help your core team of developers who have mastered the business code.

https://docs.mongodb.com/manual/release-notes/4.2-changelog/

[David S.]

I now have 10 servers on 2.2.31 and couldn't find anything today.

- On the server, bufferChatInsertsMs is set to 100

- TypingIndictor is deactivated because it led to strange error messages in 2.2.30.

I could only see the following in the log yesterday:

Dec 4 00:18:51 bbb bbb-webrtc-sfu [2658]: 2020-12-03T23: 18: 51.202Z - error: [mcs-balancer] Failed to connect to media server url = ws: //127.0.0.1 : 8888 / kurento, ip = xxxx, mediaType = main, retries = 3

Dec 4 00:18:51 bbb bbb-webrtc-sfu [2658]: 2020-12-03T23: 18: 51.203Z - error: [mcs-balancer] Failed to connect to media server url = ws: //127.0.0.1 : 8889 / kurento, ip = xxxx, mediaType = audio, retries = 3

Dec 4 00:18:51 bbb bbb-webrtc-sfu [2658]: 2020-12-03T23: 18: 51.203Z - error: [mcs-balancer] Failed to connect to media server url = ws: //127.0.0.1 : 8890 / kurento, ip = xxxx, mediaType = content, retries = 3

Dec 4 00:18:55 bbb bbb-webrtc-sfu [2658]: 2020-12-03T23: 18: 55.415Z - error: [mcs-balancer] Failed to connect to media server url = ws: //127.0.0.1 : 8888 / kurento, ip = xxxx, mediaType = main, retries = 4

Dec 4 00:18:55 bbb bbb-webrtc-sfu [2658]: 2020-12-03T23: 18: 55.416Z - error: [mcs-balancer] Failed to connect to media server url = ws: //127.0.0.1 : 8889 / kurento, ip = xxxx, mediaType = audio, retries = 4

Dec 4 00:18:55 bbb bbb-webrtc-sfu [2658]: 2020-12-03T23: 18: 55.416Z - error: [mcs-balancer] Failed to connect to media server url = ws: //127.0.0.1 : 8890 / kurento, ip = xxxx, mediaType = content, retries = 4

[David S.]

today: 1 Meeting with 227 members - total 6 Meetings with 270 users on the server

Sound clear, chat ist working, no ghosts

After the meeting, I'll take a closer look at the logs

[Anton Georgiev]

Hi all,

We have pushed additional improvements into .31 and are looking for feedback before we release this version.

Notable changes:

 - better stability for audio (specifically on FireFox) https://github.com/bigbluebutton/bigbluebutton/pull/11006

 

 - improved ListenOnly audio https://github.com/bigbluebutton/bigbluebutton/pull/10945

 

To try out this pre-release of 2.2.31, you can switch a (non-production) BigBlueButton server to use the latest build packages by running the following command

echo "deb https://ubuntu.bigbluebutton.org/xenial-220-dev22a bigbluebutton-xenial main" | sudo tee /etc/apt/sources.list.d/bigbluebutton.list

and then update the server to the latest packages using either using the docs at

   https://docs.bigbluebutton.org/2.2/install.html#upgrading-from-bigbluebutton-22

or using bbb-install.sh with the following parameter

  -v  xenial-220-dev22a

After upgrading, `sudo bbb-conf --check` should show build 2.2.31.   and the client build is 1111.

Regards,

Anton

[Ghazi TRIKI]

Hi Luiz,

I tested removing mondo 3.4 and installing percona mongodb 4.2 like you described and it did not work. Can you please provide full steps for it?

[gokhan....@gmail.com]

Hi Fred,

I really love the all parts of BBB. BUT, please do yourself a favor and DROP this MongoDB. 

I am in pursue from the very first days of this marketing miracle and all I see is people drops it in a certain point of performance/distribution/consistency. 

I know it is crazy to change an important part of the project in the middle of the progress but this a crucial decision to be made.

It is really bothers me how the data will be floating between large distributed nodes of BBB. 

There are some alternatives;

Used to work with Couchdb[1] and i can say it is quite stable now. You can't loss data and they have a fair strategy to make things distributed (of course as not as excellent choice as Riak but this is another story).

Some other alternatives should seriously evaluated in this list[2]

You can skip most of DBs because of license model such as CockroachDB, OrientDB.

RethinkDB was was quite unfinished to me when i was tested 2 years ago. But who knows for now.

Or maybe you would plan to go with Postgresql JSON mode which is good but not going to solve totally the distributed DB needs. 

How about etcd? Would it be too unstructured for the purpose?

But again please i am begging you, drop this before it is too late.

All my best o/

P.S. If you and your team say yes, i am willing to investigate alternatives in the light of compatibility, performance, consistency and installation easiness.

Jut let me know!

[1] https://couchdb.apache.org/ 

[2] https://www.educba.com/mongodb-alternatives/

 

Gokhan Boranalp aka kunthar 

[basisbit]

Please don't randomly suggest some database solution without understanding how BBB works and what its requirements are.

[Gökhan Boranalp]

Please don't randomly suggest RTFM to the old sports after spending
~30 bloody years around.
Of course I am aware of the role of db[1]. You use meteor and mongo as
a companion for HTML5.
Because you need to talk with the database directly on the frontend.
Nothing is fancy here. Meteor is also SPOF and you know this (just
skipping).
Even etcd[2] can replace Mongo sunsh*ne though. BUT you can use
PouchDB[3] for brevity of simple mindedness.
Or you can check the atmosphere for alternatives till you find a robust one.
I was dealing with NoSql databases in 2010[4]. Hope someone else makes
them better for now.

[1] https://github.com/bigbluebutton/bigbluebutton/search?q=Mongo.Collection
[2]
https://atmospherejs.com/greyarch/etcd
https://atmospherejs.com/imdark/meteor-orientdb
https://atmospherejs.com/?q=postgresql

[3] https://pouchdb.com/ (which is CouchDB)
https://forums.meteor.com/t/cloudants-couchdb-pouchdb-offline-usage/25207/3
https://linux4one.com/questions/using-pouchdb-with-mongodb
https://github.com/pouchdb/pouchdb

[4] https://www.slideshare.net/kunthar/nosql-veritabanlari (use google
translate bruh)

> --
> You received this message because you are subscribed to a topic in the Google Groups "BigBlueButton-dev" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/bigbluebutton-dev/roeuj95mFUQ/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to bigbluebutton-...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/bigbluebutton-dev/ce2d2a17-603f-49ec-b776-9161c817cb1an%40googlegroups.com.



--
--

Gokhan Boranalp aka kunthar
https://github.com/kunthar
https://slideshare.net/kunthar

\|/

[Paulo Lanzarin]

Gokhan,

Giving you a more thorough reply. And be aware that these are just my personal 3 cents. Meteor and Mongo are not my forté.

I really love the all parts of BBB. BUT, please do yourself a favor and DROP this MongoDB. 

I am in pursue from the very first days of this marketing miracle and all I see is people drops it in a certain point of performance/distribution/consistency. 

I know it is crazy to change an important part of the project in the middle of the progress but this a crucial decision to be made.

It is really bothers me how the data will be floating between large distributed nodes of BBB.

Just to clarify some fundamentals here:

1. MongoDB is not used for long term data persistence in the regular sense in BBB. It's used for livedata transfers between clients (browsers) and servers (meteor). That's achieved via
   minimongo which is a JS client side impl. which mimics the MongoDB API, stores local collections, ...
2. MongoDB is pretty intertwined with Meteor if you're using livedata sync and querying like BBB is using (in a very rampant way if I may say). So no, we can't just
   swap some other DB in because this is not the regular data storing scenario. That would work if we were using something like Apollo which is DB agnostic. Not the
   case.
   
3. Item 2 -> if we drop Mongo, how do we handle livedata? Does <your-db-of-preference> provide it? Is there a minimongo equivalent? We'd have to implement livedata
   transfer again in some other way. Meteor without Mongo works only if you're not using collection syncing like almost everything is using. The only parts that would be
   safe are some veeeery specific ones   (some whiteboard and sync video playback things) that use the Meteor websocket streamer (the rocket.chat one) to do bidirectional DDP stuff.
   

So if you're aiming at swapping MongoDB for some other database, you're targeting the wrong thing. The thing with MongoDB in your proposition would be dropping it and never looking back
at a DB in bbb-html5. And coming up with an adapted client-server signalling model.
The only place that really warrants a database in BBB is the one that holds the really core business logic (akka-apps). Anything other than that smells like data duplication.

But then again: things like these need to be thought over a lot before even thinking about doing something like it. Questions that would need to be answered with concrete data is:

  - What are we getting out of this endeavor (aka do we really need to do it or we're focusing on the wrong problem)?

  - Isn't there a more proper angle to this supposed problem (aka one that actually fixes something and can be done fast)?

  - What current technical features we have now would we lose?

  - What's the estimated work?

  - Can it be done with a gradual transition model?

s,

prlanzarin

--

You received this message because you are subscribed to the Google Groups "BigBlueButton-dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-...@googlegroups.com.

[Paulo Lanzarin]

One last point I forgot to mention that we have to consider:

  - By swapping X for Y, are we in for the long run? Does Y blended with Meteor has a guaranteed long term development

support? Or is it hacky, flakey or dying and we'll end up having to tear it apart (again) in a foreseeable future due to unpredictable hurdles?

s,

prlanzarin

[Gökhan Boranalp]

Thank you for the response Paulo. I believe you've emphasized the
right points[1] o/
It is now quite obvious to use transient data storage to pass
temporary data produced in the frontend through to the server.
I have seen this necessity long since but BBB is still not a base
project for me. I've stopped at this point.
If still core project members ask for suitable alternatives, I can
spend my time and provide alternatives.

Thank you again for this constructive discussion.


[1] "Or is it hacky, flakey or dying and we'll end up having to tear

it apart (again) in a foreseeable future due to unpredictable
hurdles?"

> You received this message because you are subscribed to a topic in the Google Groups "BigBlueButton-dev" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/bigbluebutton-dev/roeuj95mFUQ/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to bigbluebutton-...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/bigbluebutton-dev/CADG0wOBnO%3D0UK0hdHmMi_RQPM%3DmdJONrCH4eLnG7MVq3n%3D66yg%40mail.gmail.com.

[Luiz Gonzaga da Mata]

hi Ghazi Trik,

If you want to test and because it is not a BBB official, I can help you in particular.

I installed it in my lab just for testing and 3.4.24 continues in production. I tested the operation of BBB without noticing flaws or errors with Mongodb 4.4.

Percona is very well documented, without licensing costs, with support (if you wish to hire) and versions prior to 3.6 of Mongodb are discontinued: https://www.mongodb.com/support-policy

MongoDB 3.4 -> EOL in January 2020.
MongoDB 3.6 -> EOL April 2021.

I suggested to the core of developers the possibility and evaluation of adopting a new version of Mongodb that brings the use and implementation of the real mechanism of direct access to memory provided by Percona. In addition, it introduces new settings that allow you to optimize the use of resources such as, for example, TCP Fast Open (https://en.wikipedia.org/w/index.php?title=TCP_Fast_Open&oldid=922380898) and latency, among others (https://docs.mongodb.com/manual/release-notes/4.4/#networking).

"Spoiler alert: this post focus on MongoDB 3.6.X series and higher since previous versions have reached its End-of-Life (EOL)." : https://www.percona.com/blog/2020/04/17/mongodb-best-practices-2020-edition/

To work in a test environment only:

Remove Mongodb 3.4;
Install Percona Mongodb 4.4
Adjust the systemd with the start of Percona Mongodb.
Set the IP to 127.0.1.1 in /etc/mongodb.conf.
Save a copy of /usr/share/meteor/bundle/mongo-ramdisk.conf and make the specific configuration to use the engine in memory.

The mongodb service being listen on port 27017 and on IP 127.0.1.1 no changes are required on BBB.

Regards ...

 

To view this discussion on the web visit https://groups.google.com/d/msgid/bigbluebutton-dev/5b65b79e-0195-4331-951a-dcea003a1d43n%40googlegroups.com.