[SOLVED] PPv4: Need help with MySQL tuning

This forum is for Marvell Kirkwood devices such as the GoFlex Home/Net, PogoPlug v1/v2, SheevaPlug, and ZyXEL devices.

[SOLVED] PPv4: Need help with MySQL tuning

Postby winestock » Mon Feb 11, 2013 2:51 am

Since my PPv4 only has 128MB of RAM I want to tune the MySQL so that it memory is better. To help me with this I downloaded the tuning-primer.sh script. After running it the results was:
Code: Select all
   -- MYSQL PERFORMANCE TUNING PRIMER --
        - By: Matthew Montgomery -

MySQL Version 5.5.29-MariaDB-log armv5tel

Uptime = 0 days 0 hrs 32 min 8 sec
Avg. qps = 2
Total Questions = 3918
Threads Connected = 1

Warning: Server has not been running for at least 48hrs.
It may not be safe to use these recommendations

To find out more information on how each of these
runtime variables effects performance visit:
http://dev.mysql.com/doc/refman/5.5/en/server-system-variables.html
Visit http://www.mysql.com/products/enterprise/advisors.html
for info about MySQL's Enterprise Monitoring and Advisory Service

SLOW QUERIES
The slow query log is NOT enabled.
Current long_query_time = 10.000000 sec.
You have 1 out of 3939 that take longer than 10.000000 sec. to complete
Your long_query_time seems to be fine

BINARY UPDATE LOG
The binary update log is enabled
The expire_logs_days is not set.
The mysqld will retain the entire binary log until RESET MASTER or PURGE MASTER LOGS commands are run manually
Setting expire_logs_days will allow you to remove old binary logs automatically
See http://dev.mysql.com/doc/refman/5.5/en/purge-master-logs.html
Binlog sync is not enabled, you could loose binlog records during a server crash

WORKER THREADS
Current thread_cache_size = 4
Current threads_cached = 1
Current threads_per_sec = 0
Historic threads_per_sec = 0
Your thread_cache_size is fine

MAX CONNECTIONS
Current max_connections = 20
Current threads_connected = 1
Historic max_used_connections = 2
The number of used connections is 10% of the configured maximum.
You are using less than 10% of your configured max_connections.
Lowering max_connections could help to avoid an over-allocation of memory
See "MEMORY USAGE" section to make sure you are not over-allocating

INNODB STATUS
Current InnoDB index space = 1 M
Current InnoDB data space = 5 M
Current InnoDB buffer pool free = 87 %
Current innodb_buffer_pool_size = 128 M
Depending on how much space your innodb indexes take up it may be safe
to increase this value to up to 2 / 3 of total system memory

MEMORY USAGE
Max Memory Ever Allocated : 145 M
Configured Max Per-thread Buffers : 10 M
Configured Max Global Buffers : 144 M
Configured Max Memory Limit : 154 M
Physical Memory : 119 M

Max memory limit exceeds 90% of physical memory

KEY BUFFER
No key reads?!
Seriously look into using some indexes
Current MyISAM index space = 99 K
Current key_buffer_size = 32 K
Key cache miss rate is 1 : 0
Key buffer free ratio = 375809638400 %
Your key_buffer_size seems to be fine

QUERY CACHE
Query cache is enabled
Current query_cache_size = 8 K
Current query_cache_used = 8 K
Current query_cache_limit = 8 K
Current Query cache Memory fill ratio = 100.00 %
Current query_cache_min_res_unit = 4 K
MySQL won't cache query results that are larger than query_cache_limit in size

SORT OPERATIONS
Current sort_buffer_size = 32 K
Current read_rnd_buffer_size = 32 K
Sort buffer seems to be fine

JOINS
./tuning-primer.sh: line 402: export: `2097152': not a valid identifier
Current join_buffer_size = 132.00 K
You have had 16 queries where a join could not use an index properly
You should enable "log-queries-not-using-indexes"
Then look for non indexed joins in the slow query log.
If you are unable to optimize your queries you may want to increase your
join_buffer_size to accommodate larger joins in one pass.

Note! This script will still suggest raising the join_buffer_size when
ANY joins not using indexes are found.

OPEN FILES LIMIT
Current open_files_limit = 1024 files
The open_files_limit should typically be set to at least 2x-3x
that of table_cache if you have heavy MyISAM usage.
Your open_files_limit value seems to be fine

TABLE CACHE
Current table_open_cache = 100 tables
Current table_definition_cache = 400 tables
You have a total of 80 tables
You have 80 open tables.
The table_cache value seems to be fine

TEMP TABLES
Current max_heap_table_size = 16 M
Current tmp_table_size = 16 M
Of 1917 temp tables, 18% were created on disk
Created disk tmp tables ratio seems fine

TABLE SCANS
Current read_buffer_size = 32 K
Current table scan ratio = 60 : 1
read_buffer_size seems to be fine

TABLE LOCKING
Current Lock Wait ratio = 0 : 4200
Your table locking seems to be fine


The reported part of that I want to fix is:
Code: Select all
MEMORY USAGE
Max Memory Ever Allocated : 145 M
Configured Max Per-thread Buffers : 10 M
Configured Max Global Buffers : 144 M
Configured Max Memory Limit : 154 M
Physical Memory : 119 M

Max memory limit exceeds 90% of physical memory


What do I need to change in /etc/mysql/my.cnf to fix the memory usage issues?

/etc/mysql/my.cnf:
Code: Select all

# Example MariaDB config file for medium systems.
#
# This is for a system with little memory (32M - 64M) where MariaDB plays
# an important part, or systems up to 128M where MariaDB is used together with
# other programs (such as a web server)
#
# MariaDB programs look for option files in a set of
# locations which depend on the deployment platform.
# You can copy this option file to one of those
# locations. For information about these locations, do:
# 'my_print_defaults --help' and see what is printed under
# Default options are read from the following files in the given order:
# More information at: http://dev.mysql.com/doc/mysql/en/option-files.html
#
# In this file, you can use all long options that a program supports.
# If you want to know which options a program supports, run the program
# with the "--help" option.

# The following options will be passed to all MariaDB clients
[client]
#password       = your_password
port            = 3306
socket          = /var/run/mysqld/mysqld.sock

# Here follows entries for some specific programs

# The MariaDB server
[mysqld]
port            = 3306
socket          = /var/run/mysqld/mysqld.sock
skip-external-locking
#key_buffer_size = 16M
key_buffer_size = 32K
#max_allowed_packet = 1M
max_allowed_packet = 32K
#table_open_cache = 64
table_open_cache = 100
#sort_buffer_size = 512K
sort_buffer_size = 32K
net_buffer_length = 8K
#read_buffer_size = 256K
read_buffer_size = 32K
#read_rnd_buffer_size = 512K
read_rnd_buffer_size = 32K
#myisam_sort_buffer_size = 8M
myisam_sort_buffer_size = 512K
thread_cache_size = 4
max_connections=20

# Point the following paths to different dedicated disks
#tmpdir         = /tmp/

# Don't listen on a TCP/IP port at all. This can be a security enhancement,
# if all processes that need to connect to mysqld run on the same host.
# All interaction with mysqld must be made via Unix sockets or named pipes.
# Note that using this option without enabling named pipes on Windows
# (via the "enable-named-pipe" option) will render mysqld useless!
#
#skip-networking
skip-name-resolve

# Replication Master Server (default)
# binary logging is required for replication
log-bin=mysql-bin

# binary logging format - mixed recommended
binlog_format=mixed

# required unique id between 1 and 2^32 - 1
# defaults to 1 if master-host is not set
# but will not function as a master if omitted

server-id       = 1

#Set the query cache low
query_cache_limit = 8K
query_cache_size = 8K
query_cache_type = 1

#
# To configure this host as a replication slave, you can choose between
# two methods :
#
# 1) Use the CHANGE MASTER TO command (fully described in our manual) -
#    the syntax is:
#
#    CHANGE MASTER TO MASTER_HOST=<host>, MASTER_PORT=<port>,
#    MASTER_USER=<user>, MASTER_PASSWORD=<password> ;
#
#    where you replace <host>, <user>, <password> by quoted strings and
#    <port> by the master's port number (3306 by default).
#
#    Example:
#
#    CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT=3306,
#    MASTER_USER='joe', MASTER_PASSWORD='secret';
#
# OR
#
# 2) Set the variables below. However, in case you choose this method, then
#    start replication for the first time (even unsuccessfully, for example
#    if you mistyped the password in master-password and the slave fails to
#    connect), the slave will create a master.info file, and any later
#    change in this file to the variables' values below will be ignored and
#    overridden by the content of the master.info file, unless you shutdown
#    the slave server, delete master.info and restart the slaver server.
#    For that reason, you may want to leave the lines below untouched
#    (commented) and instead use CHANGE MASTER TO (see above)
#
# required unique id between 2 and 2^32 - 1
# (and different from the master)
# defaults to 2 if master-host is set
# but will not function as a slave if omitted
#server-id       = 2
#
# The replication master for this slave - required
#master-host     =   <hostname>
#
# The username the slave will use for authentication when connecting
# to the master - required
#master-user     =   <username>
#
# The password the slave will authenticate with when connecting to
# the master - required
#master-password =   <password>
#
# The port the master is listening on.
# optional - defaults to 3306
#master-port     =  <port>
#
# binary logging - not required for slaves, but recommended
#log-bin=mysql-bin

# Uncomment the following if you are using InnoDB tables
#innodb_data_home_dir = /var/lib/mysql
#innodb_data_file_path = ibdata1:10M:autoextend
#innodb_log_group_home_dir = /var/lib/mysql
# You can set .._buffer_pool_size up to 50 - 80 %
# of RAM but beware of setting memory usage too high
#innodb_buffer_pool_size = 16M
#innodb_additional_mem_pool_size = 2M
# Set .._log_file_size to 25 % of buffer pool size

#innodb_log_file_size = 5M
#innodb_log_buffer_size = 8M
#innodb_flush_log_at_trx_commit = 1
#innodb_lock_wait_timeout = 50

[mysqldump]
quick
max_allowed_packet = 16M

[mysql]
no-auto-rehash
# Remove the next comment character if you are not familiar with SQL
#safe-updates

[myisamchk]
#key_buffer_size = 20M
key_buffer_size = 16K
#sort_buffer_size = 20M
sort_buffer_size = 16K
#read_buffer = 2M
read_buffer = 16K
#write_buffer = 2M
write_buffer = 16K

[mysqlhotcopy]
interactive-timeout
Last edited by winestock on Tue Feb 12, 2013 4:08 am, edited 1 time in total.
Pogoplug Series 4 / Linux-Kirkwood 3.10.10-2
winestock
 
Posts: 134
Joined: Mon Nov 05, 2012 12:03 am

Re: PPv4: Need help with MySQL tuning

Postby moonman » Mon Feb 11, 2013 3:33 am

It's almost impossible to optimize mysql on this kind of hardware. I've tried mariadb (optimized mysql) on E02 with !256 ram and either way it was painfully slow. If you reduce memory usage - it is slow because cache is almost non-existant, if you allow it to use more memory, then half of the cache goes onto swap which is slow as well. If you still like to use it, start with disabling things you don't need. For example if you use myisam then disable innodb module.
Pogoplug V4 | GoFlex Home | Raspberry Pi B 512 | CuBox-i4 Pro | ClearFog | BeagleBone Black | Odroid U2 | Odroid C1 | Odroid XU4
-----------------------------------------------------------------------------------------------------------------------
[armv5] Updated U-Boot | |[armv5] How to install my.pogoplug.com service | [armv5] NAND Rescue System
moonman
Developer
 
Posts: 2956
Joined: Sat Jan 15, 2011 3:36 am
Location: Calgary, Canada

Re: PPv4: Need help with MySQL tuning

Postby winestock » Tue Feb 12, 2013 4:08 am

I got it figured out. What really helped me was first running:
Code: Select all
mysqladmin -u root variables


From this I figured out that I needed to tweek:
Code: Select all
innodb_buffer_pool_size = 32M
innodb_additional_mem_pool_size = 2M


After restarting mysqld and re-running the tuning-primer.sh script:
Code: Select all
MEMORY USAGE
Max Memory Ever Allocated : 67 M
Configured Max Per-thread Buffers : 8 M
Configured Max Global Buffers : 66 M
Configured Max Memory Limit : 74 M
Physical Memory : 119 M
Max memory limit seem to be within acceptable norms


mariadb seem to run pretty well on the PPv4. Of course it is not any speed demon but I already knew that. Command respond while mysqld is running is now where it should be, quick.
Pogoplug Series 4 / Linux-Kirkwood 3.10.10-2
winestock
 
Posts: 134
Joined: Mon Nov 05, 2012 12:03 am

Re: [SOLVED] PPv4: Need help with MySQL tuning

Postby moonman » Tue Feb 12, 2013 4:19 am

It maybe OK for simple things, but it couldn't run PHP + MySql+lighttpd + some CMS reasonably fast. Or maybe things have changed a lot since a year ago. The important part is if you are satisfied with the performance for your use. And you seem so ;)
Pogoplug V4 | GoFlex Home | Raspberry Pi B 512 | CuBox-i4 Pro | ClearFog | BeagleBone Black | Odroid U2 | Odroid C1 | Odroid XU4
-----------------------------------------------------------------------------------------------------------------------
[armv5] Updated U-Boot | |[armv5] How to install my.pogoplug.com service | [armv5] NAND Rescue System
moonman
Developer
 
Posts: 2956
Joined: Sat Jan 15, 2011 3:36 am
Location: Calgary, Canada

Re: [SOLVED] PPv4: Need help with MySQL tuning

Postby winestock » Tue Feb 12, 2013 5:31 am

moonman wrote:It maybe OK for simple things, but it couldn't run PHP + MySql+lighttpd + some CMS reasonably fast. Or maybe things have changed a lot since a year ago. The important part is if you are satisfied with the performance for your use. And you seem so ;)


I am only using mariadb for simply storing XBMC library information. The only other resource that I use on the PPv4 is UNFS3 for the access to the media for streaming movies.
Pogoplug Series 4 / Linux-Kirkwood 3.10.10-2
winestock
 
Posts: 134
Joined: Mon Nov 05, 2012 12:03 am

Re: [SOLVED] PPv4: Need help with MySQL tuning

Postby rhester72 » Wed May 01, 2013 5:02 pm

If you disable InnoDB completely and just run MyISAM, you can get mysql memory down by a factor of about 12x...seriously. Give it a try (assuming you don't need row-level locking, etc. - for a simple use case, MyISAM is fine).

Rodney
rhester72
 
Posts: 35
Joined: Tue Apr 30, 2013 4:24 pm

Re: [SOLVED] PPv4: Need help with MySQL tuning

Postby winestock » Sat May 11, 2013 2:32 pm

rhester72 wrote:If you disable InnoDB completely and just run MyISAM, you can get mysql memory down by a factor of about 12x...seriously. Give it a try (assuming you don't need row-level locking, etc. - for a simple use case, MyISAM is fine).

Rodney


I disabled INNODB engine and my memory usage went from 35% down to 15%. Thanks.
Pogoplug Series 4 / Linux-Kirkwood 3.10.10-2
winestock
 
Posts: 134
Joined: Mon Nov 05, 2012 12:03 am


Return to Marvell Kirkwood

Who is online

Users browsing this forum: No registered users and 0 guests