Jump to content

swap after convertion to innodb


Recommended Posts

Hello ! ^_^

After converting my database to innodb, I noticed that my server is swapping, but this problem happens only when there is a WHM backup running. This backup is resource intensive and when it begins, I see the swap value steadily rising from 0 to about 600. And everyday, the swap rises each time a backup is running...

What are the solutions, in your opinion ?

 

Here is what ./mysqlmymonlite.sh mysqltuner returned :

Quote

 

-------------------------------------------------------------
System MySQL monitoring stats
mysqlmymonlite.sh - 0.5.4 mysqlmymon.com
compiled by George Liu (eva2000) vbtechsupport.com
-------------------------------------------------------------

Report Generated:
mar. mars 29 14:21:50 CEST 2016

-------------------------------------------------
mysqltuner output
-------------------------------------------------
mysqltuner.pl [found]
 >>  MySQLTuner 1.6.7 - Major Hayden <major@mhtx.net>
 >>  Bug reports, feature requests, and downloads at http://mysqltuner.com/
 >>  Modified by George Liu (eva2000) at http://vbtechsupport.com/
 >>  Run with '--help' for additional options and output filtering

[--] Skipped version check for MySQLTuner script
[OK] Currently running supported MySQL version 5.6.29-log
[OK] Operating on 64-bit architecture

-------- System Linux Recommendations  ---------------------------------------
Look for related Linux system recommandations
[--] There is 44 listening port(s) on this server.
[!!] There is too many listening ports: 44 > 10
[!!] There is Apache like server running on 80 or 443 port.
[OK] No Application server runing on 8080 or 8443 port.

-------- Storage Engine Statistics -------------------------------------------
[--] Status: +ARCHIVE +BLACKHOLE +CSV -FEDERATED +InnoDB +MEMORY +MRG_MYISAM +MyISAM +PERFORMANCE_SCHEMA
[--] Data in MyISAM tables: 1G (Tables: 723)
[--] Data in InnoDB tables: 17G (Tables: 425)
[--] Data in MEMORY tables: 0B (Tables: 6)
[!!] Total fragmented tables: 108

-------- Performance Metrics -------------------------------------------------
[--] Up for: 10h 15m 20s (5M q [138.655 qps], 282K conn, TX: 60G, RX: 8G)
[--] Reads / Writes: 76% / 24%
[--] Binary logging is disabled
[--] Total buffers: 27.5G global + 14.2M per thread (1000 max threads)
[OK] Maximum reached memory usage: 28.0G (44.54% of installed RAM)
[OK] Maximum possible memory usage: 41.5G (65.92% of installed RAM)
[OK] Slow queries: 0% (68/5M)
[OK] Highest usage of available connections: 3% (34/1000)
[OK] Aborted connections: 0.00%  (0/282777)
[!!] Query cache should be disabled by default due to mutex contention.
[OK] Sorts requiring temporary tables: 0% (1 temp sorts / 85K sorts)
[!!] Joins performed without indexes: 2270
[OK] Temporary tables created on disk: 21% (8K on disk / 39K total)
[OK] Thread cache hit rate: 99% (34 created / 282K connections)
[OK] Table cache hit rate: 99% (1K open / 1K opened)
[OK] Open file limit used: 8% (1K/17K)
[OK] Table locks acquired immediately: 99% (2M immediate / 2M locks)

-------- ThreadPool Metrics --------------------------------------------------
[--] ThreadPool stat is disabled.

-------- Performance schema --------------------------------------------------
[--] Performance schema is enabled.

-------- MyISAM Metrics ------------------------------------------------------
[!!] Key buffer used: 23.0% (493M used / 2B cache)
[OK] Key buffer size / total MyISAM indexes: 2.0G/445.5M
[!!] Read Key buffer hit rate: 89.9% (990K cached / 100K reads)
[!!] Write Key buffer hit rate: 41.9% (134K cached / 78K writes)

-------- AriaDB Metrics ------------------------------------------------------
[--] AriaDB is disabled.

-------- InnoDB Metrics ------------------------------------------------------
[--] InnoDB is enabled.
[OK] InnoDB buffer pool / data size: 25.0G/17.8G
[OK] InnoDB buffer pool instances: 25
[!!] InnoDB Used buffer: 35.27% (577813 used/ 1638375 total)
[OK] InnoDB Read buffer efficiency: 99.98% (2113678258 hits/ 2114203741 total)
[OK] InnoDB Write log efficiency: 97.35% (17287701 hits/ 17758956 total)
[OK] InnoDB log waits: 0.00% (0 waits / 471255 writes)

-------- TokuDB Metrics ------------------------------------------------------
[--] TokuDB is disabled.

-------- Galera Metrics ------------------------------------------------------
[--] Galera is disabled.

-------- Replication Metrics -------------------------------------------------
[--] No replication slave(s) for this server.
[--] This is a standalone server..

-------- Recommendations -----------------------------------------------------
General recommendations:
    Consider dedicating a server for your database installation with less services running on !
    Consider dedicating a server for Web server in production !
    Run OPTIMIZE TABLE to defragment tables for better performance
    MySQL started within last 24 hours - recommendations may be inaccurate
    Adjust your join queries to always utilize indexes. Please note this
    calculation is made by adding Select_full_join + Select_range_check
    status values and triggered when the total >250
Variables to adjust:
    query_cache_type (=0)
    join_buffer_size (> 2.0M, or always use indexes with joins)

Report Complete:
mar. mars 29 14:21:54 CEST 2016
----------------------------

 

 

Thank you. ^_^

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...