The document discusses various topics related to optimizing MySQL performance, including database engines, basic settings, useful utilities, and queries. It begins by describing different MySQL storage engines like InnoDB, MyISAM, Memory, NDB and others. It then covers important configuration settings like query_cache_size, innodb_buffer_pool_size, and others. Utilities for MySQL performance analysis and tuning are presented, such as tuning-primer.sh, mysql-tuner.pl, and tools from the maatkit collection. Best practices for query optimization are also covered, such as using ORM frameworks, proper indexing, and making queries concrete. The document concludes by providing contact details for the author.

1. MySQL:ОсновыоптимизацииилиЧтодолжен знать каждыйразработчик

2. АгниславОнуфрийчукОбо мне

3. АгниславОнуфрийчукВеб-разработчикОбо мне

4. АгниславОнуфрийчукВеб-разработчикЛюблю девушекОбо мне

5. АгниславОнуфрийчукВеб-разработчикЛюблю девушекНе люблю MS Internet Exporerи OperaОбо мне

6. Ктоработает с MySQL?О вас

7. Ктоработает с MySQL?КтоиспользуетMyISAM?О вас

8. Ктоработает с MySQL?КтоиспользуетMyISAM?Ктоещё не используетInnoDB?О вас

9. Ктоработает с MySQL?КтоиспользуетMyISAM?Ктоещё не используетInnoDB?Кто не знает про my.ini/my.cnf?О вас

10. Здесьзнают толк в оптимизацииMySQLО PortaOne

11. Здесьзнают толк в оптимизацииMySQLЗдесьзнают толк в девушкахО PortaOne

12. Здесьзнают толк в оптимизацииMySQLЗдесьзнают толк в девушкахЗдесьзнают толк в программистахО PortaOne

13. Здесьзнают толк в оптимизацииMySQLЗдесьзнают толк в девушкахЗдесьзнают толк в программистахЗдесьзнают толк в after-parties.О PortaOne

14. Здесьзнают толк в оптимизацииMySQLЗдесьзнают толк в девушкахЗдесьзнают толк в программистахЗдесьзнают толк в after-parties.О PortaOne

15. Начнём?

16. ОптимизацияMySQL

17. Всё плохо. ОптимизацияMySQL

18. Сегоднямы не поговорим о…

19. ШардингеСегоднямы не поговорим о…

20. ШардингеЖелезеСегоднямы не поговорим о…

21. ШардингеЖелезеОперационных системахСегоднямы не поговорим о…

22. ШардингеЖелезеОперационных системахФайловых системахСегоднямы не поговорим о…

23. Сегоднямыпоговорим о…

24. Движках (engines)Сегоднямыпоговорим о…

25. Движках (engines)Базовых настройкахСегоднямыпоговорим о…

26. Движках (engines)Базовых настройкахПолезныхутилитахСегоднямыпоговорим о…

27. Движках (engines)Базовых настройкахПолезныхутилитахЗапросахСегоднямыпоговорим о…

28. Движках (engines)Базовых настройкахПолезныхутилитахЗапросахИ о чём-нибудьприятномСегоднямыпоговорим о…

29.  Engines Settings Utilities Queries Girls Roadmap

30.  Engines Settings Utilities Queries Girls Roadmap

31.  Engines Settings Utilities QueriesRoadmap

32.  Engines Settings Utilities QueriesRoadmap

33. Engines

34. WTF?Engines

35. WTF? It’s cool!Engines

36. InnoDB/XtraDBMyISAM/MariaMemoryNDBCSVBlackholeEngines

37. Extremely fastNot-transactionalTable-level lockingNo BLOB/TEXT data typesEngines: Memory

38. Extremely fastTransactionalRow-level lockingGood scaling capabilitiesEngines: NDB

39. Simple data exchangeNo table partitioningNo NULL values (since 5.1.23)Engines: CSV

40. Extremely fast (faster then Memory/NDB)TransactionalAll types of indexesLow-cost storageEngines: Blackhole

41. Default for years (up to 5.5)Non-TransactionalTable-level lockingFull-text search indexesFast readEngines: MyISAM

42. TransactionalRow-level lockingForeign keysSimple performance tuningEngines: InnoDB

43. All InnoDB feature plus:“Out-of-box” better performanceMost powerful performance tuning“Troubleshoot without guesswork”Engines: XtraDB

44.  Engines Settings Utilities QueriesRoadmap

45. There hundreds of them…Settings

46. There hundreds of them…but a couple of them are enough for usSettings

47. Using memory is better than using diskThe main point is…

48. query_cache_sizeDoes matter for SELECT-dedicated server32M is generally enoughSettings

49. innodb_buffer_pool_sizeGive all you can:Servers: 50-75% of available memoryDev PC: 25-50% of available memorySettings

50. innodb_log_file_sizeMake your log files big.128M/256M is a good valueSettings

51. innodb_log_buffer_sizeHow often we’ll flush log data to disk4M is a good value unless you’re piping large blobs.Settings

52. innodb_flush_log_at_trx_commit0 – write log buffer to file and flush it to disk every second1 – write&flush to disk for every transaction2 – write for every transaction and flush every secondSettings

53. innodb_thread_concurrency=8Just use this valueSettings

54. innodb_flush_method=O_DIRECTAvoid double bufferingSettings

55. innodb_file_per_tableUse it if you don’t have tons of tablesSettings

56.  Engines Settings Utilities QueriesRoadmap

57. tuning-primer.shmysql-tuner.plmaatkitinnotopUtilities

58. http://www.day32.com/MySQL/tuning-primer.sh

59. SLOW QUERIESCurrent long_query_time = 10 sec.You have 526 out of 36204146 that take longer than 10 sec. to completeThe slow query log is NOT enabled.Your long_query_time may be too high, I typically set this under 5 sec.tuning-primer.sh

60. QUERY CACHEQuery cache is enabledCurrent query_cache_size = 8 MCurrent query_cache_used = 7 MCurrent query_cach_limit = 1 MCurrent Query cache fill ratio = 89.38 %However, 254246 queries have been removed from the query cache due to lack of memoryPerhaps you should raise query_cache_sizeMySQL won't cache query results that are larger than query_cache_limit in size tuning-primer.sh

61. TEMP TABLESCurrent max_heap_table_size = 16 MCurrent tmp_table_size = 32 MOf 35170 temp tables, 74% were created on diskEffective in-memory tmp_table_size is limited to max_heap_table_size.Perhaps you should increase your tmp_table_size and/or max_heap_table_size to reduce the number of disk-based temporary tablesNote! BLOB and TEXT columns are not allow in memory tables.If you are using these columns raising these values might not impact your ratio of on disk temp tables. tuning-primer.sh

62. http://mysql-tuner.plmysql-tuner.pl

63. -------- Storage Engine Statistics ---------------------[--] Status: -Archive +BDB -Federated +InnoDB -ISAM -NDBCluster[--] Data in MyISAM tables: 19M (Tables: 90)[!!] InnoDB is enabled but isn't being used[!!] BDB is enabled but isn't being used[!!] Total fragmented tables: 18mysql-tuner.pl

64. -------- Performance Metrics ---------------------------[--] Up for: 16m 37s (6K q [6.059 qps], 146 conn, TX: 54M, RX: 665K)[--] Reads / Writes: 62% / 38%[--] Total buffers: 298.0M global + 6.3M per thread (100 max threads)[OK] Maximum possible memory usage: 929.2M (26% of installed RAM)[OK] Slow queries: 0% (0/6K)[OK] Highest usage of available connections: 5% (5/100)[OK] Key buffer size / total MyISAM indexes: 256.0M/2.3M[!!] Key buffer hit rate: 91.3% (1K cached / 101 reads)[OK] Query cache efficiency: 97.6% (5K cached / 5K selects)mysql-tuner.pl

65. -------- Recommendations -------------------------------General recommendations:Add skip-innodb to MySQL configuration to disable InnoDBAdd skip-bdb to MySQL configuration to disable BDBRun OPTIMIZE TABLE to defragment tables for better performanceMySQLstarted within last 24 hours - recommendations may be inaccurateEnable the slow query log to troubleshoot bad queriesmysql-tuner.pl

66. maatkithttp://www.maatkit.org/

67. maatkitmk-error-logmk-log-playermk-index-usagemk-query-advisormk-query-digestmk-query-profiler… (>30)

68. maatkit: mk-error-logCount Level Message ===== ======= ======================================= 5 info mysqld started 4 info mysqld version info 3 info InnoDB: Started 2 info mysqld ended 1 unknown Number of processes running now: 0 1 error [ERROR] /usr/sbin/mysqld: unknown variable 'ssl-ke 1 error [ERROR] Failed to initialize the master info struc

69. maatkit: mk-log-playermk-log-player does two things: it splits MySQL query logs into session files and it plays (executes) queries in session files on a MySQL server.

70. maatkit: mk-index-usageThis tool connects to a MySQL database server, reads through a query log, and uses EXPLAIN to ask MySQL how it will use each query. When it is finished, it prints out a report on indexes that the queries didn't use.

71. maatkit: mk-query-advisormk-query-advisor examines queries and applies rules to them, trying to find queries that look bad according to the rules. It reports on queries that match the rules, so you can find bad practices or hidden problems in your SQL.

72. maatkit: mk-query-digest # pct total min max avg 95% stddev median # Count 0 2 # Exec time 13 1105s 552s 554s 553s 554s 2s 553s # Lock time 0 216us 99us 117us 108us 117us 12us 108us # Rows sent 20 6.26M 3.13M 3.13M3.13M3.13M 12.73 3.13M # Rows exam 0 6.26M 3.13M 3.13M3.13M3.13M 12.73 3.13M… # Query_time distribution # 1us # 10us # 100us # 1ms # 10ms # 100ms # 1s # 10s+ #############################################################

73. maatkit: mk-query-profilermk-query-profiler reads a file containing one or more SQL statements or shell commands, executes them, and analyzes the output of SHOW STATUS afterwards. It then prints statistics about how the batch performed. For example, it can show how many table scans the batch caused, how many page reads, how many temporary tables, and so forth.

74. http://code.google.com/p/innotop/innotop

75.  Engines Settings Utilities QueriesRoadmap

76. Queries

77. use ORMsuse Indexesbe concrete (limit yourself)get a map!Queries

78. why?use ORMs

79. experiencesafetyclear codespeeding developmentportabilityuse ORMs

80. why?use Indexes

81. CREATE TABLE employee (employee_number char(10) NOT NULL,firstnamevarchar(40), surname varchar(40), address text,tel_novarchar(25), salary int(11),overtime_rateint(10) NOT NULL);use Indexes

82. use IndexesNOT using PRIMARY KEY Using PRIMARY KEYEXPLAIN SELECT employee_number, firstname, surname FROM employee WHERE id=1000\G id: 1select_type: SIMPLE table: employee type: constpossible_keys: PRIMARY key: PRIMARYkey_len: 4 ref: const rows: 1 Extra: id: 1select_type: SIMPLE table: employee type: ALLpossible_keys: NULL key: NULLkey_len: NULL ref: NULL rows: 10000 Extra: Using where

83. use IndexesALTER TABLE employee ADD INDEX(surname, firstname);SELECT overtime_rate FROM employeeWHERE surname='Madida';SELECT overtime_rate FROM employee WHERE firstname='Mpho';SELECT overtime_rate FROM employee WHERE surname='Madida' and firstname="Mpho";SELECT overtime_rate FROM employee WHERE firstname="Mpho" and surname='Madida';

84. use IndexesALTER TABLE employee ADD INDEX(surname, firstname);SELECT overtime_rate FROM employeeWHERE surname='Madida';SELECT overtime_rate FROM employee WHERE firstname='Mpho';SELECT overtime_rate FROM employee WHERE surname='Madida' and firstname="Mpho";SELECT overtime_rate FROM employee WHERE firstname="Mpho" and surname='Madida';

85. use Indexesand be concreteselect … WHERE year(my_date) > 2010select … where email LIKE “%@gmail.com”select * from table;select * from table limit 10000;select col1 from table where id > 0;insert into table values(‘1’, ‘bla’);

86. create table `ids` ( `id` int(11) NOT NULL AUTO_INCREMENT, `id1` int(11) NOT NULL,`id2` int(11) DEFAULT NULL, …, PRIMARY KEY (`id`)) ENGINE=InnoDB;SELECT COUNT(*) FROM `ids`;SELECT COUNT(`id`) FROM `ids`;SELECT COUNT(`id1`) FROM `ids`;SELECT COUNT(`id2`) FROM `ids`;get a map!

87.  EnginesSettings Utilities QueriesRoadmap

88. Questions?

89. Contactsvcardagnislav @gmailskypetwitterfacebookvkontaktelivejournal