gcache | gcache is the middleware of gorm , gorm has cache | Caching library

Either you use some dedicated tool for this like Ansible (lineinfile) or you have to code it yourself.

Rules for memory allocation.

• Do not allocate so much RAM that swapping will occur. Swapping is terrible for MySQL/MariaDB performance.
• Do adjust innodb_buffer_pool_size such that most of RAM is in use during normal time and even for spikes in activity. (I often say "set it to 70% of available RAM", but you are asking for more details.)
• Do not bother changing other settings; they add to the complexity of "getting it right".

There are 3 situations (based on innodb_buffer_pool_size and dataset size):

• Tiny dataset -- buffer_pool is bigger than necessary --> wasting some of RAM, but so what; it is not useful for anything else. And it give you some room for growth.
• Medium-sized dataset -- Most activity is done in RAM; the system will run nicely.
• Big dataset -- The system may be I/O-bound. Adding RAM is a costly and brute force solution. However, some software techniques (eg, better indexes) may help, such as this for WordPress and WooCommerce.

Based on your cmake output, I'd guess that you're using a version of FindGStreamer.cmake cribbed from WebKit. If that's the case, the variable you want to use is GSTREAMER_MPEGTS_INCLUDE_DIRS. Note the lack of a hyphen in the variable name.

If that's not the case, use a simple message() statement before the use of a variable to show you its value during the cmake step.

In your CMakeLists.txt:

You're calculating the per-thread memory usage wrong. Those variables (and tmp_table_size which you didn't include) are not all used at the same time. Don't add them up. And even if you were to add them up, at least two might be allocated multiple times for a single query, so you can't just sum them anyway.

Basically, the memory usage calculated by MySQLTuner is totally misleading, and you shouldn't believe it. I have written about this before: What does "MySQL's maximum memory usage is dangerously high" mean by mysqltuner?

If you want to understand actual memory usage, use the PERFORMANCE_SCHEMA, or the slightly easier to read views on it, in the SYS schema.

The documentation for PS or SYS is pretty dense, so instead I'd look for better examples in blogs like this one:

https://www.percona.com/blog/2020/11/02/understanding-mysql-memory-usage-with-performance-schema/

Redis persistences are configured in server side not client side. And it is not possible to have different persistence policy for one Redis instance.

For you case, if you want to have different persistence policy(RDB, AOF, or just disabled), you can set up multiple redis servers and create different redis client for those servers.

For node-redis, you can create different client for different servers as below:

I could find out, I missed the fact that periodic backup was running on the node via Mariabackup tool. During that time node de-syncs itself from cluster for consistency.

I noticed you SET Open Files handles in ubuntu to 1024 when you ran ulimit -n 1024. Your system needs many more available Open File handles to support your 4650 innodb tables. Suggestion ulimit -n 24000 and then check settings with ulimit -a (to list current limits). I am looking forward to analyzing your data next week from production instance.

Suggestion for your ulimit -a to consider please

ulimit -n 24000 # from 1024 to enable more OS file handles to be active.

The above is dynamic with Linux OS. Stop/Start services would have access to the handles. To make this persistent across OS shutdown/restart, review this url for similar OS instructions. These instructions set 500000 for the file-max, please set your capacity at 24000 for now. ulimit please set to 24000, which will allow MySQL to use requested limits and have spares for other apps

https://glassonionblog.wordpress.com/2013/01/27/increase-ulimit-and-file-descriptors-limit/

Set innodb_buffer_pool_size to about 70% of available RAM. The 4.4G suggested by mysqltuner will handle all your current data. If you expect it to grow, then give it more. This setting will probably help with I/O (not CPU).

(Actually "InnoDB Read buffer efficiency: 95.00% (920105182 hits/ 968548737 total)" says that the paultry 128M buffer_pool seems to handle the "working set" adequately.)

You cannot tune for "optimize for better CPU usage". You can find the slow queries and work on indexing (especially 'composite' indexes) and query formulation. Those will help with CPU.

http://mysql.rjweb.org/doc.php/mysql_analysis