MySQL Forums
Forum List  »  Performance

Re: 5.5 results
Posted by: Peter Brawley
Date: May 06, 2021 02:17PM

MySQL diagnostics 5.5
DB sizes
InnoDB | 0.02 GB | 0.00 GB | 0.02 GB |
CSV    | 0.00 GB | 0.00 GB | 0.00 GB |
MyISAM | 0.00 GB | 0.00 GB | 0.00 GB |
TOTALS | 0.02 GB | 0.00 GB | 0.02 GB |
MySQL version                           5.5.62          
Slow queries/sec                        unknown         
Queries not using indexes               0               
Queries needing full table scans/sec    0               
InnoDB buffer pool inefficiency         0.0004          Grow innodb_buffer_pool_size if > 2% or if innodb_buffer_pool_size < 70% of RAM
InnoDB page reads / pool read requests  0.0004          Grow innodb_buffer_pool_size if > 2% or if innodb_buffer_pool_size < 70% of RAM
InnoDB log file thrashing               0.6699          Best is near 0.5; grow innodb_log_file_size if well under 0.5, shrink if much larger
Time between InnoDB log rotation        12:12:12        Grow log size if < 30 min, shrink if > 60 min, but see here.
Est. best InnoDB log file size          32MB            Average hour of writes rounded up to 32MB boundary
InnoDB buffer pool reads / sec          0.0106          If high, increase Innodb_buffer_pool_size up to 70% of RAM
MyISAM key buffer size                  354MB           Min pre-8.0=40MB, max(64-bit) depends on OS and memory
MyISAM buffer hit ratio                 0               If < 10, grow key_buffer_size
MyISAM key write ratio                  0               Much higher than 1 suggests a disk write bottleneck
MyISAM key read rate                    0               
Query cache hits/inserts                0               If low, consider disabling the cache
Query cache spills / sec                0               If low, consider disabling the cache
Query cache hits / sec                  0               If low, consider disabling the cache
Temp tables created/sec                 0               If > 20, find the queries responsible and optimise them, 
Temp tables created on disk/Questions   0.0068          If > .05, try growing join_buffer_size, optimise responsible queries, 
Temp tables created on disk/sec         0               If high, grow tmp_table_size, max_heap_size. Avoid Blobs, use HEAP tables in queries
Database changes / connection           0.13            Use db.table syntax
Processes/connection                    0.25            If high, grow thread_cache_size
Files opened/sec                        0               If > 5, increase table_open_cache
Queries/sec                             0.01            Thousands is busy: you may need better hardware
Writes/sec                              0               If, over 50/sec, better disk hardware may be needed
Insert statements/sec                   0               
Inserts/sec                             1.04            Can be up to 20K/sec with efficient memory use, see here
Next table row requests/sec             0               If high, queries need optimising esp. with covering indexes
Sampling time                           16:27:39        If < 2h in a typical use period, re-do
Max MySQL RAM use                       1.8GB           Must be less than RAM available to MySQL
Available RAM                           unknown         If less than Max MySQL memory use, more memory needed

InnoDB basic stats

innobuffpool:       1024MB
bytes read/sec      33
reads/sec           0
bytes/read          20282
writes/sec          0
bytes/write         47660
bytes written/sec   548
rollback %          0
buffpool free       97%



Edited 3 time(s). Last edit at 05/06/2021 02:20PM by Peter Brawley.

Options: ReplyQuote


Subject
Views
Written By
Posted
Re: 5.5 results
86
May 06, 2021 02:17PM
128
May 09, 2021 11:28AM
85
May 09, 2021 12:27PM
76
May 10, 2021 01:42AM
88
May 10, 2021 10:17AM
80
May 10, 2021 11:15AM
98
May 10, 2021 02:39PM
100
May 11, 2021 06:58AM
72
May 11, 2021 11:42AM
98
May 11, 2021 01:14PM
76
May 11, 2021 02:05PM


Sorry, only registered users may post in this forum.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.