MySQL Forums
Forum List  »  InnoDB

Re: mysql 8.0.27 went crash
Posted by: y y
Date: April 23, 2022 06:52PM

Hello. I run the analysis follow https://www.artfulsoftware.com/infotree/tip.php?id=1339&r=1 。 And the results are as follows:

Database load:

engine	data	indexes	total
InnoDB	84.08 GB	58.25 GB	142.33 GB
CSV	0.00 GB	0.00 GB	0.00 GB
TOTALS	84.08 GB	58.25 GB	142.33 GB

Performance metrics:

item		rate
Slow queries/sec		       0
Unindexed queries/sec		       0
Full table scans/sec		       240.63
Total InnoDB load / buffer pool size   14.23
InnoDB buffer pool inefficiency	       0.21
InnoDB pages read and buffer pool      0.24
InnoDB log thrashing		       0.01
Est. best InnoDB log file size	       32MB
Mins between InnoDB log rotation       4.91
Query cache hits/sec		
Query cache spills/sec		
MyISAM buffer hit ratio		
MyISAM key read rate		       0
MyISAM key write ratio		
MyISAM query cache hits/inserts		
Temp tables created/sec		       0.02
Database changes/connection		
Processes/connection		       0.41
Queries/sec		               1266.14
Inserts/sec		
Table scan next row seeks/sec	       138037.52
InnoDB buffer reads/sec		       1175.37
Files opened/sec		       0
Created tmp disk tables/sec	       0.02
Created_tmp_disk_tables/Queries	       0
Max MySQL RAM use		       107.64


innodb 
iops	buffpoolsize	bufferpoolpctfee	bytesread/s	read/s	bytes/read	byteswritts	writes/S	bytes/write
1658	10.0GB	0	947	16298.2	17	6851	470.1	15



Edited 1 time(s). Last edit at 04/25/2022 12:18AM by Peter Brawley.

Options: ReplyQuote


Subject
Views
Written By
Posted
1984
y y
April 19, 2022 07:09PM
593
April 19, 2022 10:58PM
540
y y
April 20, 2022 01:41AM
472
y y
April 20, 2022 01:50AM
530
April 20, 2022 10:19AM
509
y y
April 20, 2022 06:20PM
470
April 20, 2022 06:53PM
Re: mysql 8.0.27 went crash
450
y y
April 23, 2022 06:52PM
493
April 25, 2022 12:22AM
505
April 25, 2022 05:50AM
547
April 25, 2022 09:48AM
509
y y
April 25, 2022 08:36PM


Sorry, you can't reply to this topic. It has been closed.

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.