vicidial.org

Mysql Memory usage too high on vicidial 8 34.99 % with no system load ( no agents logged just a fresh install from iso ViciBox_v8.x86_64-8.0.1.iso) I just installed 2 server and the same issue on both, server running vicibox 7 mysql usage normal


VERSION: 2.14-647a
BUILD: 171229-2309
© 2017 ViciDial Group

Mysql will use as much memory as you tell it to, and as much as the server will allow. The /etc/my.cnf file is for configuring things like Mysql memory usage.

mflorell wrote:Mysql will use as much memory as you tell it to, and as much as the server will allow. The /etc/my.cnf file is for configuring things like Mysql memory usage.

you re right at that point , but what I mean is I have the same configuration on mysql for vicibox 7 and 8 and the memory consumption is really high on version 8

On vicibox 7 it is around 9% and on vicibox 8 34 % so there is a huge difference , and know system requiments seems to be higher to use vicinbox 8


[mysqld]
log_bin=/var/lib/mysql/mysql-bin
binlog_format=mixed
server-id=1
relay-log = /var/lib/mysql/mysqld-relay-bin
slave-skip-errors = 1032,1690,1062
datadir=/var/lib/mysql
sql_mode=NO_ENGINE_SUBSTITUTION
port = 3306
socket = /var/run/mysql/mysql.sock
skip-external-locking
skip-name-resolve
connect_timeout=60
long_query_time=3
slow_query_log=1
slow-query-log-file=/var/log/mysql/mysqld-slow.log
max_connections=512
key_buffer_size=2G
max_allowed_packet=16M
table_open_cache=512
table_definition_cache=2048
open_files_limit=24576
sort_buffer_size=4M
net_buffer_length=8K
read_buffer_size=4M
read_rnd_buffer_size=16M
myisam_sort_buffer_size=128M
join_buffer_size=1M
thread_cache_size=100
query_cache_size=32M
thread_concurrency=8
default-storage-engine=MyISAM
expire_logs_days=3
concurrent_insert=2
myisam_repair_threads=2
myisam_use_mmap=1
skip-innodb
delay_key_write=ALL
max_write_lock_count=1

MySQL routinely uses as much memory as it can (in fact it will often eat ALL the memory), but it will mark unneeded memory as available for harvesting by the system. In the meantime if that memory happens to have a data page that can save a disk read, mysql runs much faster.

Your system has only 2G of RAM. If it had (for instance) 16G of RAM, it would be using a much smaller percentage.

If you are not experiencing a failure as a result of the memory usage, it is likely that you are outsmarting yourself trying to fix something that isn't broken and the result will be "less memory usage" and a system that is no longer optimal.

IE: You're gonna break it while trying to fix something that's not an error.

I advise caution. Check to see if there are queries being run that are slow or overloading the system (show processlist). If not, leave it alone. IMHO