mariadb-tokudb.png

User Rating: 5 / 5

Star ActiveStar ActiveStar ActiveStar ActiveStar Active

So after doing some readings, I saw that there are several advantages to using TokuDB over InnoDB when we are dealing with huge databases. The thing here is that using that TokuDB requires jemalloc to run. Since CentOS 7 and 8 are systemd enabled using the methods advertised on most websites won't work.

I will write here what I did to enable it,

server-on-diet.png

User Rating: 5 / 5

Star ActiveStar ActiveStar ActiveStar ActiveStar Active

After running successfully a medium-to-big cluster, one of your concerns is your database keeps growing. If you do not do anything, sooner than later there won't be a server that can host your FusionPBX database.

The good news about this is that it is very easy to know why the database grows so fast. It is logic, more customers, more calls, therefore, your database detailed record grows faster. In technical words, your v_xml_cdr table grows and grows.

Depending on the kind of customers you are hosting, CDR can be very valuable or depreciable. Depending on the country you are, by law, you may be required to store a CDR record somewhere. Somewhere not in your production database. So, your solution is to archive them. If someone asks for them, you will deal with that later.

server-on-diet.png

User Rating: 5 / 5

Star ActiveStar ActiveStar ActiveStar ActiveStar Active

When you run a successful PBX with FusionPBX, one of your problems is to keep it on diet. Depending on your server sizing, this issue may come soon or later, but it will arrive. I am talking about disk space.

There are two points to cover:

  1. Database
  2. Recordings