Recommended 10 MyISAM source code examples (collection)

一、架构设计11、主从服务器可以使用不同的存储引擎。Master上使用InnoDB,利用事务、行级锁等高级特性,Slave上使用MyISAM，读性能更好，节省内存，容易备份。还可以分别使用不同的数据类型，例如Master上用varchar,Slave用char,不仅节省空间，还可以利用MyISAM的静态表特性。2、M-S-Muti Slave方案中，中继Slave还可以使用BlackHole存储引擎。BlackHole存储引擎只记录日志，不写数据。利用这个特点可以让中继日志性能提升很多。但是，这种方案不支持GTIDs迷失下的Replication,因为BlackHole只能搭配StateMent格式的二进制日志,Row和Mixed格式都不可用。3、在读写分离的设计中,主从服务器可以采用不同的索引方案。Master可以只保留主键或唯一索引等保证数据关系的索引。而Salve针对查询做索引优化。

1. 浅谈 两种架构 核心架构设计

简介：一、架构设计11、主从服务器可以使用不同的存储引擎。Master上使用InnoDB,利用事务、行级锁等高级特性,Slave上使用MyISAM，读性能更好，节省内存，容易备份。还可以分别使用不同的数据类型，例如Master上用varchar,Slave用char,不仅节省空间，还可以利用MyISAM的静态表特性。2、M-S-Muti Slave方案中，中继Slave还可以使用BlackHole存储引...

2. 10篇有关MYSQL的文章推荐

简介：本文是MySQL优化系列文章的第一篇缓存优化的续篇，为大家更为详细的介绍缓存优化的方方面面，希望大家能够喜欢MySQL 内部处处皆缓存，等什么时候看了MySQL的源码，再来详细的分析缓存的是如何利用的。这部分主要将各种显式的缓存优化：查询缓存优化结果集缓存排序缓存join 连接缓存表缓存Cache 与表结构定义缓存Cache表扫描缓存bufferMyISAM索引缓存buffer日志缓存预读机制延迟...

3. 缓存优化如何使用？总结缓存优化实例用法

简介：本文是MySQL优化系列文章的第一篇缓存优化的续篇，为大家更为详细的介绍缓存优化的方方面面，希望大家能够喜欢MySQL 内部处处皆缓存，等什么时候看了MySQL的源码，再来详细的分析缓存的是如何利用的。这部分主要将各种显式的缓存优化：查询缓存优化结果集缓存排序缓存join 连接缓存表缓存Cache 与表结构定义缓存Cache表扫描缓存bufferMyISAM索引缓存buffer日志缓存预读机制延迟...

4. 有关性能指标的10篇内容推荐

简介：下面小编就为大家带来一篇MySQL几点重要的性能指标计算和优化方法总结。小编觉得挺不错的，现在就分享给大家，也给大家做个参考。一起跟随小编过来看看吧1 QPS计算(每秒查询数)针对MyISAM引擎为主的DBMySQL> show GLOBAL status like 'questions';+---------------...

5. 关于派生表的详细介绍

Introduction: In some scenarios when MySQL processes requests, the server creates internal temporary tables. That is, the table is processed in memory using the MEMORY engine, or stored on disk using the MyISAM engine. If the table is too large, the server may transfer the temporary table in memory to the disk. About derived tables When the main query contains a derived table, or when the select statement contains a union clause, or when the select statement contains an order by clause for one field (a group by clause for another field), in order to complete the query, MySQL You need to automatically...

6. MySQL transaction processing example explanation

Introduction: Not all engines support transaction processing As mentioned in Chapter 21, MySQL supports several basic database engines. As discussed in this chapter, not all engines support explicit transaction management. MyISAM and InnoDB are the two most commonly used engines. The former does not support explicit transaction management, while the latter does. This is why the sample tables used in this book were created to use InnoDB rather than the more commonly used MyISAM. If your application requires transaction processing capabilities, be sure to use the correct engine type. Transaction processing can

7. Introduction to full-text search in MySQL

Introduction: Understanding Full-Text Search Not All Engines Support Full-Text Search As mentioned in Chapter 21, MySQL supports several basic database engines. Not all engines support full-text search as described in this book. The two most commonly used engines are MyISAM and InnoDB. The former supports full-text search, while the latter does not. This is why, although most of the sample tables created in this book use InnoDB, one sample table (the productnotes table) uses MyISAM. You should keep this in mind if your application requires full-text search capabilities.

8. Explanation on the six major differences between the Mysql storage engine InnoDB and Myisam

Introduction: The difference in the composition of MyISAMInnoDB: Each MyISAM is stored as three files on the disk. The name of the first file begins with the name of the table, and the extension indicates the file type. The .frm file stores table definitions. The extension of the data file is .MYD (MYData). The extension of the index file is .MYI (MYIndex).

9. Analysis of the differences between the Mysql storage engine InnoDB and MyISAM

Introduction: I have reprinted an article before about how to choose mysql storage engine. Today I saw a summary on the Internet, which is not bad!

10. Detailed introduction to MySQL specifying the path of each partition

##Introduction: You can specify its own storage path for each partition of the partition table. For the innodb storage engine table, you can only specify the data path, because the data and index are stored in a file. For the MYISAM storage engine, you can specify it separately. Data files and index files

[Related Q&A recommendations]:

linux - How to ensure that mysql data is not lost after a failure occurs?

mysql MyISAM concurrent insert?

php - mysql command cannot export the database

MySQL update select is slow

linux - MySQL storage engine selects InnoDB and MyISAM

The above is the detailed content of Recommended 10 MyISAM source code examples (collection). For more information, please follow other related articles on the PHP Chinese website!