How often should applications be subjected to load or load?

Question

Is there a rule about how often an application should be stressed or stressed? I usually do this before introducing a new version when the hardware changes or when it is expected that the expected number of users will change.

But today I am asked if this is standard practice for an application that is in production, even if no changes have been made. If so, how often?

Answer 1

It really depends on how you want to contact him for the needs of your company. Personally, we load our daily integration (test) builds - just like builds. After the assembly runs at approximately 1a, we will also test it for load. Our goal is to primarily look for built-in changes in performance. Even if we do not make changes to the code, the servers on which the code is tested still receive updates / patches / patches / service packs / etc. In the worst case, when it is automated, it provides additional historical data.

( ), , . , ( ) , , , .

, , ? , , , . , , .

Answer 2

, , , - .

. . . "" . , , - .

- - . . , - ganglia. .

Answer 3

, , - - , , - , , .

Answer 4

: , . , (.. ). . , - !

, , , , , .

, BrowserMob, -, Selenium- X . , .

Answer 5

, ... , , , . , .

, .

Answer 6

, . , . , , . , , .
, , .

Answer 7

, , .

Answer 8

- ant, , , , - , , , , , .

, .

- , , , , QA, , .

, , , , , , , , .

junitperf -.

Answer 9

I think we do not want to emphasize the “Notepad” of the test. This is a joke. Do not pay attention =).

Stress testing is not for all applications. :-)

Answer 10

If your software can kill someone, I think you need to.

Imagine that someone is dying because the blood does not flow due to some timeout in the system.

"Timeout.exception: your heart is no longer coming. Please try again later."