CN112783785A - General test method for Nosql database performance - Google Patents
General test method for Nosql database performance Download PDFInfo
- Publication number
- CN112783785A CN112783785A CN202110136989.9A CN202110136989A CN112783785A CN 112783785 A CN112783785 A CN 112783785A CN 202110136989 A CN202110136989 A CN 202110136989A CN 112783785 A CN112783785 A CN 112783785A
- Authority
- CN
- China
- Prior art keywords
- module
- performance
- database
- configuration
- log
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 20
- 238000012812 general test Methods 0.000 title claims abstract description 11
- 238000011056 performance test Methods 0.000 claims abstract description 31
- 238000012360 testing method Methods 0.000 claims abstract description 22
- 238000012544 monitoring process Methods 0.000 claims description 7
- 238000010998 test method Methods 0.000 claims 5
- 238000012545 processing Methods 0.000 description 2
- 238000012550 audit Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/41—Compilation
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Software Systems (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention provides a general test method for Nosql database performance, wherein a specified database type, database parameters and performance test indexes are specified in a configuration file in a configuration module; the Client module is started, and the configuration in the configuration file is initialized and read; the Client module reads the configuration file and calls a corresponding database driver module; the Drivers module can connect the database according to the database parameters and types in the configuration file and start a performance test; the Monitor module starts to Monitor the performance index of the database server and reports the performance index to the Log module; the Log module outputs Log information to a file and reports result information of the Monitor module to the Client module; according to the general test method for the Nosql database performance, a user can directly obtain a desired performance index and the real-time use condition of the resource of a tested system only by knowing the type of the database to be tested and the data volume information of the test.
Description
Technical Field
The invention belongs to the technical field of data processing, and particularly relates to a general test method for Nosql database performance.
Background
Currently, database performance testing tools such as Redis, Mongodb, HBase, and elastic search of Nosql (non-relational database) are different, for example, Redis is tested by using Redis-benchmark, Mongodb is tested by using ycsb, HBase is tested by using ycsb, and elastic search is tested by using rally; testing different Nosql databases requires knowing how the corresponding tools are used, learning cost is particularly high, and checking of real-time use conditions of resources of a system to be tested in a testing process is not supported.
Disclosure of Invention
In view of this, the present invention is directed to a general testing method for performance of a Nosql database, so as to solve the problem that in the prior art, a user needs to know the Nosql database additionally and does not support checking the real-time use condition of the resources of a system under test in the testing process.
In order to achieve the purpose, the technical scheme of the invention is realized as follows:
a general test method for Nosql database performance comprises the following steps:
s1: defining the type and performance test index of a database to be tested;
s2: specifying a database type, a database parameter and a performance test index in a configuration file in a configuration module;
s3: the Client module is started, and the configuration in the configuration file is initialized and read;
s4: the Client module reads the configuration file and calls a corresponding database driver module;
s5: the Drivers module can connect the database according to the database parameters and types in the configuration file and start a performance test;
s6: the Monitor module starts to Monitor the performance index of the database server and reports the performance index to the Log module;
s7: the Log module outputs Log information to a file and reports result information of the Monitor module to the Client module;
s8: and the Client module displays the performance test result.
Further, the Client module is an entrance program.
Further, the configuration module can read information in the configuration file.
Further, the Drivers module is a performance testing tool integrating different databases of Nosql.
Further, the Monitor module is a monitoring tool integrated with various operating systems.
Further, the Log module writes the execution process of the performance testing tool, the server information, the test data information and the performance testing result into a Log file.
Compared with the prior art, the general test method for the performance of the Nosql database has the following advantages:
(1) according to the general test method for the Nosql database performance, a user does not need to spend learning time to know different Nosql performance test tools, and the user can obtain a desired performance index and the real-time use condition of the resource of a tested system very intuitively only after knowing the type of the database to be tested and the data volume information of the test.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate an embodiment of the invention and, together with the description, serve to explain the invention and not to limit the invention. In the drawings:
fig. 1 is a schematic diagram of a general test method for performance of a Nosql database according to an embodiment of the present invention.
Detailed Description
It should be noted that the embodiments and features of the embodiments may be combined with each other without conflict.
In the description of the present invention, it is to be understood that the terms "center", "longitudinal", "lateral", "up", "down", "front", "back", "left", "right", "vertical", "horizontal", "top", "bottom", "inner", "outer", and the like, indicate orientations or positional relationships based on those shown in the drawings, and are used only for convenience in describing the present invention and for simplicity in description, and do not indicate or imply that the referenced devices or elements must have a particular orientation, be constructed and operated in a particular orientation, and thus, are not to be construed as limiting the present invention. Furthermore, the terms "first", "second", etc. are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first," "second," etc. may explicitly or implicitly include one or more of that feature. In the description of the present invention, "a plurality" means two or more unless otherwise specified.
In the description of the present invention, it should be noted that, unless otherwise explicitly specified or limited, the terms "mounted," "connected," and "connected" are to be construed broadly, e.g., as meaning either a fixed connection, a removable connection, or an integral connection; can be mechanically or electrically connected; they may be connected directly or indirectly through intervening media, or they may be interconnected between two elements. The specific meaning of the above terms in the present invention can be understood by those of ordinary skill in the art through specific situations.
The present invention will be described in detail below with reference to the embodiments with reference to the attached drawings.
The noun explains:
nosql (Nosql ═ Not Only SQL): the meaning is not only SQL, is a brand new database concept, and generally refers to a non-relational database.
Configuration: software installation in a Linux environment is not an easy thing; if the source code is compiled and then installed, the matters are more complicated; courses for installing various kinds of software are very common at present; however, the problem of installing various software is solved by firmly mastering basic knowledge, and the configuration script configuration tool is one of the bases and is the basic application of the tool of the autoconf.
Use of Log: regardless of the programming language used, the log output is almost ubiquitous, and in summary, logs have roughly the following uses:
problem tracing: the log not only comprises some bugs of the program, but also can find problems when the configuration is installed;
and (3) state monitoring: by analyzing the logs in real time, the running state of the system can be monitored, and problems can be found and processed early;
and (4) safety audit: the auditing is mainly embodied in safety, and whether unauthorized operation exists can be found by analyzing the log.
A general test method for Nosql database performance comprises the following steps: the method comprises the following steps:
s1: defining the type and performance test index of a database to be tested, and determining a performance test model;
s2: specifying a database type, database parameters and performance test indexes in a configuration file in a configuration module, uniformly configuring an entry by using parameters, and configuring all required parameters at one time;
s3: the Client module is started, and initializes and reads the configuration in the configuration file, and can automatically read the configuration parameters;
s4: the Client module reads the configuration file and calls a corresponding database driver module, so that the configuration parameters can be automatically analyzed;
s5: the Drivers module can connect the database according to the database parameters and types in the configuration file, starts the performance test and can automatically select a corresponding database performance test tool to start to connect the database for the performance test;
s6: the Monitor module starts to Monitor the performance index of the database server and reports the performance index to the Log module, and complete resource monitoring and data arrangement are carried out;
s7: the Log module outputs Log information to a file, and reports result information of the Monitor module to the Client module, so that the execution process of the tool is effectively restored;
s8: the Client module displays the performance test result, so that a user does not need to spend learning time to know different Nosql performance test tools, and the user can intuitively obtain the desired performance index and the real-time use condition of the resource of the tested system only by knowing the type of the database to be tested and the data volume information to be tested;
the Client module is an entry program, and after the Client module is started, the configuration in the configuration module is read to call the corresponding Driver module to perform performance test and test result recovery, and the Monitor module is called to show the real-time use condition of the tested database resources, so that the visual performance test result can be obtained in one key mode;
the configuration module can read information in the configuration file, such as an IP address, a port number, an account number, a database name, a driver type, data volume of performance test, a test type and the like of a database, can unify parameter configuration entries, and complete all required parameters by one-time configuration;
the Drivers module is a performance testing tool integrating different Nosql databases, uniform parameter configuration and performance indexes are encapsulated, and the Drivers module can execute corresponding performance tests according to the configuration transmitted by the configuration module; after the test is finished, the driver module reports the performance test result to the Client module, the Client module displays the performance test result, mainstream performance test tools are integrated, corresponding tools are called immediately according to the test requirement, and the cost of learning each tool is saved;
the Monitor module is a monitoring tool integrating various operating systems, after the Client module calls the Monitor module, the Monitor module automatically uploads the monitoring tool to a tested database server and starts to collect resource use conditions such as a CPU (central processing unit), a memory, a disk IO (input/output) and the like, the resource use conditions of the server are reported to the Client module, and the Client module displays the resource use conditions, complete resource monitoring and data arrangement and displays a readable performance test result for a user;
the Log module writes the execution process, the server information, the test data information and the performance test result of the performance test tool into a Log file, and the test record is reserved, so that the execution process of the tool can be effectively restored, and test evidence is provided.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like that fall within the spirit and principle of the present invention are intended to be included therein.
Claims (6)
1. A general test method for Nosql database performance is characterized in that: the method comprises the following steps:
s1: defining the type and performance test index of a database to be tested;
s2: specifying a database type, a database parameter and a performance test index in a configuration file in a configuration module;
s3: the Client module is started, and the configuration in the configuration file is initialized and read;
s4: the Client module reads the configuration file and calls a corresponding database driver module;
s5: the Drivers module can connect the database according to the database parameters and types in the configuration file and start a performance test;
s6: the Monitor module starts to Monitor the performance index of the database server and reports the performance index to the Log module;
s7: the Log module outputs Log information to a file and reports result information of the Monitor module to the Client module;
s8: and the Client module displays the performance test result.
2. The universal test method for the performance of Nosql databases of claim 1, wherein: the Client module is an entrance program.
3. The universal test method for the performance of Nosql databases of claim 1, wherein: the configuration module can read information in the configuration file.
4. The universal test method for the performance of Nosql databases of claim 1, wherein: the Drivers module is a performance testing tool integrated with different Nosql databases.
5. The universal test method for the performance of Nosql databases of claim 1, wherein: the Monitor module is a monitoring tool integrated with various operating systems.
6. The universal test method for the performance of Nosql databases of claim 1, wherein: and the Log module writes the execution process, the server information, the test data information and the performance test result of the performance test tool into a Log file.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110136989.9A CN112783785A (en) | 2021-02-01 | 2021-02-01 | General test method for Nosql database performance |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110136989.9A CN112783785A (en) | 2021-02-01 | 2021-02-01 | General test method for Nosql database performance |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112783785A true CN112783785A (en) | 2021-05-11 |
Family
ID=75760260
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110136989.9A Pending CN112783785A (en) | 2021-02-01 | 2021-02-01 | General test method for Nosql database performance |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112783785A (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103729361A (en) * | 2012-10-12 | 2014-04-16 | 百度在线网络技术（北京）有限公司 | Method and device for testing performance of database |
| CN106843965A (en) * | 2017-01-20 | 2017-06-13 | 郑州云海信息技术有限公司 | The system and installation method of a kind of automated installation of system testing tool |
| CN110457202A (en) * | 2019-06-28 | 2019-11-15 | 武汉迎风聚智科技有限公司 | Quickly establish the TPC-E test method and actuator device of ODBC connection |
| CN110851357A (en) * | 2019-11-04 | 2020-02-28 | 紫光云技术有限公司 | Test data automatic construction method based on multiple database types |
| CN111090572A (en) * | 2019-12-18 | 2020-05-01 | 紫光云(南京)数字技术有限公司 | System and method for performing performance test on MySQL database |
-
2021
- 2021-02-01 CN CN202110136989.9A patent/CN112783785A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103729361A (en) * | 2012-10-12 | 2014-04-16 | 百度在线网络技术（北京）有限公司 | Method and device for testing performance of database |
| CN106843965A (en) * | 2017-01-20 | 2017-06-13 | 郑州云海信息技术有限公司 | The system and installation method of a kind of automated installation of system testing tool |
| CN110457202A (en) * | 2019-06-28 | 2019-11-15 | 武汉迎风聚智科技有限公司 | Quickly establish the TPC-E test method and actuator device of ODBC connection |
| CN110851357A (en) * | 2019-11-04 | 2020-02-28 | 紫光云技术有限公司 | Test data automatic construction method based on multiple database types |
| CN111090572A (en) * | 2019-12-18 | 2020-05-01 | 紫光云(南京)数字技术有限公司 | System and method for performing performance test on MySQL database |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6598183B1 (en) | Software tool for automated diagnosis and resolution of problems of voice, data and VoIP communications networks | |
| CN107688530B (en) | Software testing method and device | |
| US7734637B2 (en) | Method and system for automatic detection of monitoring data sources | |
| CN112965871A (en) | Vehicle fault prompt information acquisition method and device and storage medium | |
| US20150220426A1 (en) | Performance tests in a continuous deployment pipeline | |
| CN103793326A (en) | Assembly test method and device | |
| CN111913133A (en) | Distributed fault diagnosis and maintenance method, device, equipment and computer readable medium | |
| CN110750458A (en) | Big data platform testing method and device, readable storage medium and electronic equipment | |
| KR102179847B1 (en) | System and method for providing diagnosis of infra | |
| CN110489319B (en) | Interface performance test analysis method and storage medium | |
| CN111290941A (en) | Method and device for testing multiple interfaces, computing equipment and medium | |
| CN112269697B (en) | Equipment storage performance testing method, system and related device | |
| CN113553238A (en) | Cloud platform resource exception automatic processing system and method | |
| CN109871368B (en) | Database detection method, database detection device, computer device and storage medium | |
| US9253069B2 (en) | Method and system for testing configuration of environments | |
| KR101830936B1 (en) | Performance Improving System Based Web for Database and Application | |
| CN112783785A (en) | General test method for Nosql database performance | |
| CN114115168A (en) | Fault injection test system | |
| CN115248782B (en) | Automatic testing method and device and computer equipment | |
| CN112416762A (en) | API test method and device, equipment and computer readable storage medium | |
| CN114064510A (en) | Function testing method and device, electronic equipment and storage medium | |
| CN112069202A (en) | SQL performance analysis method, system, device and medium based on tracking technology | |
| CN112015637A (en) | Application performance management system and method | |
| CN110399411B (en) | Data source switching method, device, equipment and computer readable storage medium | |
| CN114968829B (en) | Full link pressure test method, electronic device and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210511 |
|
| RJ01 | Rejection of invention patent application after publication |