mongodb vs mysql performance

MySQLDBA Tutorial: Mysql Performance Optimization-cache parameter optimization bitsCN.com Databases are IO-intensive applications. their primary responsibilities are data management and storage. We know that the time for reading a database from the memory is microseconds, while reading an IO from a common hard disk is in milliseconds. The difference between the two is three orders of magnitude. Therefore, t

feel crawling when using the default value for large data volumes. The InnoDB buffer pool caches data and indexes, so you do not need to leave space for the system cache. If you only use InnoDB, you can set this value to 70%-80% of the memory. Similar to key_buffer, if the data volume is small and does not increase much, do not set this value too high or increase the memory usage. Innodb_additional_mem_pool_sizeThis effect is not very obvious, at least when the operating system can reasonably

This article summarizes and introduces MySQL Performance Optimization in detail. For more information, see the following code: SELECT id, nick_name FROM user, user_group WHERE user_group.group_id = 1 and user_group.user_id = user. id order by user_group.gmt_create desc limit 100,20; Solution 2: SELECT user.id,user.nick_name FROM(SELECT user_idFROM user_groupWHERE user_group.group_id=1ORDER BY gmt_create

Various locking mechanisms have emerged to ensure data integrity. The locking mechanism determines the concurrent processing capability and performance of a database. The locking mechanism of the database is simply a rule designed by the database to ensure data consistency and make various shared resources orderly when they are accessed concurrently. Three types of locking mechanisms are available: Row-level locking, page-level locking, and table-leve

This article mainly introduces the MySQL performance analysis tool profile tutorial, this article describes how to use MySQLprofile, does not involve specific sample analysis, if you need it, you can refer to the analysis of SQL execution overhead, which is an important means to optimize SQL. In MySQL databases, you can configure the profiling parameter to enable

Five configuration parameters that affect MySQL Performance: bitsCN.com The following articles mainly introduce the five configuration parameters that closely affect MySQL Performance. I saw the five configuration parameters that closely affect MySQL

choose a master multi-slave architecture; 3. A Redis Sentinel chooses a low match. Advantage: The Redis official own HA solution, written by Redis authors, has disadvantage: After failover occurs, the client needs to correct the address manually Redis Medium High-availability architecture Scenario: Redis master-slave +haproxy load Balancing server resources: At least 3 PC servers deploy Redis master-slave, two PC server deployments Haproxy Pros: Read-write separation, scale-out slave Cons: Ma

MySQL supports a large number of data types, so choosing the right data type is critical to getting high performance. Then understand the pros and cons of various types first!First, type introduction1. Integral type　　The integral type is: tinyint,smallint,mediumint,int,bigint . They account for 8,16,24,32,64 storage space respectively. The integer range that can be stored is -2^ (N-1) to 2^ (N-1)-1, where N

MYSQL development performance research-batch data insertion optimization method, mysql batch I. What problems have we encountered? In standard SQL, we usually write the following SQL insert statement. INSERT INTO TBL_TEST (id) VALUES(1); Obviously, this method is also feasible in MYSQL. However, when we need to insert

] mysqldump [Options]--databases [options] DB1 [DB2 DB3] ... mysqldump [Options]--all-databases [options] 1 "MyISAM engine, can directly copy data sheet. 2 "mysqldump: Data export to SQL statement 3 "SELECT * FROM table1 to outfile '/tmp/table1.txt '; 4 "Recovery: Load Data infile '/tmp/table1.txt ' into table table1; 4,mysqlimport Mysqlimport [OPTIONS] Database textfile ... The Mysqlimport program is a tool program that will store text data in a specific format (such as data files generated

; set [global] Variable name = value;Permanently definedVim/etc/my.cnf[Mysqld]Variable name = value....: Wq#systemctl Restart MysqldMySQL architecture?Connection poolSQL interfaceAnalyzerOptimizerQuery cacheStorage EngineFile systemManagement toolsHow does the MySQL service process query requests?4 The SQL query command of the query database written by the program is unreasonable, resulting in slow database processingEnable slow query log on the datab

The usage policy and optimization (high-performance index policy) bitsCN.com in this chapter are based on the above theoretical basis. In fact, once you understand the mechanism behind the index, therefore, selecting a high-performance policy becomes pure reasoning and can understand the logic behind these policies. Sample database To discuss the index policy, a database with a small amount of data is requi

For some systems with a large data volume, the database faces problems in addition to the low query efficiency, but also the long data warehouse receiving time. Especially for the report system, the time spent on data import may be several hours or dozens of hours every day. Therefore, MySQL is used to optimize the database insertion performance. For some systems with a large data volume, the database fac

Label:Because in many times the intranet scan does not have the authorized win's good, a little bit of weak password scanner (generate reports, a variety of services), compiled into a plug-in, and then made a MONGODB scan plug-in.X-scan after loading:Mongodb.plug:Mysql.plug:Scanning:X-scan SCAN Plugs1. mysql Weak password scan2. MongoDB Unauthorized ScanX-scan Do

Eight methods for optimizing MySQL database performance (2) bitsCN.com Create table customerinfo(CustomerID int not null,Primary key (CustomerID)) TYPE = INNODB;Create table salesinfo(SalesID int not null,CustomerID int not null,Primary key (CustomerID, SalesID ),Foreign key (CustomerID) REFERENCES customerinfo(CustomerID) ON DELETECASCADE) TYPE = INNODB; Note the parameter "on delete cascade" in the exampl