Tags: des io ar using SP on problem CTI ADHardware and Software EnvironmentMySQL version: 5.1.50, driver version: 5.1.6 (the latest 5.1.13 has a lot of assorted problems)MongoDB version: 1.6.2, driver version: 2.1Operating system: Windows XP SP3 (This effect should not be small)Cpu:intel Core2 E6550 2.33GMemory: 2G (Enough)MySQL startup parameters: Bin\mysqld--no-defaults--console--character-set-server=utf8--max_connections=1000--max_user_ connections
Tags: IDT concurrent scenarios MongoDB multithreaded Data test report God 10gServer Size: Single-node deployment, disk 1T, memory 128G Concurrent Import Size: 1, multithreading concurrent import CSV file 2,csv file 10,000, 100,000, 1 million, 2 million rows of records 4 sizes 3, each CSV corresponds to a collection Concurrency Query Scale 1, multi-threaded concurrent query different collection 2, divided into full table query and local query two scena
, you can directly add the index input: {"name": 1, "Age":-1.
Do not drop the table after creating an index.
2. OptimizationCodeImproper use of the method will significantly affect mongdb performance. Here I will list my usage experience:
A. simply update the data using template. updatefirst () or template. updatemulti () instead of template. findandmodify ();
B. Simply add a data operation and use 'template. insert () 'instead of 'template. Sa
After the new Web Machine node was added to the project, it was found that the performance of its MongoDB cluster was beginning to suffer, and the response time of MongoDB became very long during the peak period of the request.
The monitoring found that the number of MongoDB connections reached around 1100~1500 at its
1.mongo Lock Overview:Features of each version lock:当前版本 生产版本最高是 2.6.7[Production Release (2.6.7)] 开发版本是 3.0.0-rc7[Development Releases (unstable)3.0.0] Version Ps:mysql's InnoDB and Oracle support row locks. The highest version of production release is 2.6.7, which supports only library-level locks, and when a MongoDB is in the write state, other operations are done. Although MONGO has a library lock, it can still maintain high
Label:Do you encounter performance problems when using MongoDB? Here is a summary of the five steps of MongoDB performance optimization, which I hope will help. First step: Find the slow statement In general, query statements are too slow and performance problem bottlenecks
,64.0g memory, centos6.5 64-bit.1. Mongod into the line test, query speed 13000QPS..2. Router into the line test, query speed 10000QPS.Summary: Finally find the problem root knot, clientcpu the number of cores determines the speed of MongoDB query.Conclusion1. Li Yun's cloud host has made certain restrictions, resulting in. Anyway, set the system. Database configuration, all. Unable to break through. An order of magnitude of QPS.The number of 2.CLIENT
represents the number of documents scanned.2 If the information is incomplete, you can try to use a different version of the client.
Optimizer: Profiler
Open function.
1 can be started by adding parameters:-profiler=12 Execution Command: Db.setprofilinglevel (1)
Query record: Db.system.profiler.find ()
Performance Tuning Overview
Performance Optimizati
1. Display Server Status: Db.serverstatus () 2. MongoDB can monitor data through profile to optimize it.
Check whether the profile function is currently turned on: Db.getprofilinglevel () returns level, value 0|1|2, meaning: 0 for off, 1 for slow command, 2 for all
Open profile function: Db.setprofilinglevel (level,slowms); #level等级. At level 1 o'clock, the slow command defaults to SLOWMS (unit ms)(that is, execution time is greater than
using PowerShell Call Mtools Analyze MongoDB performance and send mailProblem Description:In MongoDB daily operations, it is often necessary to view the trend graph, slow query, overflow statement, and connection source of the number of connections.Solution:1. Mount the Windows Backup machine directory to the MongoDB l
, centos6.5 64-bit. Ucloud, router: 16 CPU, 64.0g memory, centos6.5 64-bit1. perform a test on mongod. The query speed is 13000qps.2. perform a test on the router. The query speed is QPS.. Conclusion: the root cause of the problem is found. The number of client cpu cores determines the mongodb query speed.Conclusion1. Alibaba Cloud's cloud host has some restrictions, resulting in no matter how to set the system or database configuration, it cannot bre
This article introduces how to use $ or and sort () to query performance analysis in MongoDB. If you need it, let's take a look at it. If you don't design thousands of records for your website, the server will be stuck.
The Code is as follows:
Copy code
Mongos> db. find ({"user": "jhon"}). sort ({"name ":1}). limit (100). explain (){"Cursor": "BtreeCursor user_1 ","Nscanned": 10100,"
Tags: wan theory large number of connections coded pad memory alt modeThe performance test of MONGODB billion data volume was carried out, and the following items were tested:(All inserts are single-threaded and all reads are multithreaded) 1) Normal insertion performance (the inserted data is about 1KB per piece) 2) Bulk Insert
Tags: blog point stat log roo exec DMI default primaryOne, write performance test script [Email protected] bin]#/mongo 172.27.8.118:40000 sharding_2:primary> Use adminSwitched to DB adminSharding_2:primary> Db.auth (' WLAN ', ' WLAN ') Sharding_2:primary> Use Estestdbnew Switched to DB estestdbnew for (Var i=0;i; i++) {Db.estestdbnew.insert ({name:"new", Age:999})} One, bulk write performance test script v
third query, $ or is used separately, and the performance is good.
Later in the official forum to ask a question, learned that there is a bug: https://jira.mongodb.org/browse/SERVER-1205
It will be modified in the future. Record it today.
Forum reply:
I believe the issue you are running into is expressed in this JIRATicket: https://jira.mongodb.org/browse/SERVER-1205
I believe the query optimizer is choosing to use the name index andWalk it backwards
to say, about the introduction of information, installation and other please pull to the end of the article, I attached some information, later if necessary to share. This article focuses on MongoDB paged query, why? Paging is a common killer, bad, customer scold, manager scold.Traditional SQL PagingTraditional SQL paging, all the solutions are almost row_number, for the needs of a variety of sorting, complex query scenarios, Row_number is the killer
Because do not enter the database, this article does not represent MongoDB performance, only in this and IO to do a simple comparison of the performance is not scientific, but also from the side to explain a certain problem, to the development of a certain hint.
Attached: This test and in early 2012, due to the late entry of the blog, may be different, welcome to
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
info-contact@alibabacloud.com
and provide relevant evidence. A staff member will contact you within 5 working days.