Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Performance #80

Open
dialex opened this issue Jan 15, 2019 · 1 comment
Open

Performance #80

dialex opened this issue Jan 15, 2019 · 1 comment
Labels
6.fields
Projects
Writing
Milestone
v0.6-Fields

Comments

@dialex
Copy link
Owner

dialex commented Jan 15, 2019 •
edited
Loading

@dialex dialex added this to the v0.6-Fields milestone Jan 15, 2019
@dialex dialex added this to Untriaged in Writing via automation Jan 15, 2019
@dialex
Copy link
Owner Author

dialex commented Jun 15, 2021

Here's what I found:

  • Performance testing: You measure the system's speed under normal traffic
  • Load testing: (a sub-set of performance testing) You keep increasing the traffic until it fails. The goal is to find the upper limit supported by the system
  • Stress testing: (a sub-set of performance testing) Same as load but you continue to increase traffic ever after it fails, plus you also force failures. The goal, goal is to check how the system recovers from failures.

Sources:
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
6.fields
1 participant
@dialex