About stress testing (how strong is SQLite? Stress Testing on my 2 machines)

Modern projects seem to be unable to leave the database forever-therefore, the industry is calling for professional DBAs.

Http://www.matrix.org.cn/blog/sgsoft/archives/001079.html

Stress Testing is nothing more than three parts:

Multi-request-multi-thread, distributed

Large data volume-cyclic, batch submission

Ultra-long transactions-asynchronous response and message-oriented middleware Performance Management

In writing database test cases, the effect of loops must be one-time. That is to say, 10 thousand cycles must be thrown to the database in the shortest period, which leads to real pressure.

. Net supports loops in the same way as other languages. The reason for slow loops is the logic of loop execution, rather than the Loop itself.

How to dynamically increase the batch submission volume to test the database strength so that the test results are meaningful. DBA can easily put pressure on the database-simply use SQL loops, but DBA cannot easily find the best running point of the database, especially for OLAP systems. On the contrary, it is convenient for programmers who write stress testing programs, because the stress can be adjusted dynamically. (LoadRunner has such advanced functions, but this software is too expensive)

Today's performance monitoring and stress testing are almost monopolized by foreign software. Is it feasible to implement a Chinese software system that supports distributed cluster stress testing?

I have been busy with projects recently, and I have no time to update them. I am busy today. I saw a good source of inspiration and responded to it.