Trail: FundamentalRules

Performance Testing : FundamentalRules

KnowledgeBase :: Categories :: PageIndex :: RecentChanges :: RecentlyCommented :: Login/Register
Most recent edit on 2010-11-29 12:22:05 by Admin

No differences.


Edited on 2010-11-29 12:21:53 by Admin

Additions:

The three fundamental rules of performance testing



Deletions:

3 Fundamentals Rules of Performance Testing

The three fundamental rules of performance testing




Edited on 2010-11-29 12:21:27 by Admin

Additions:
Provide your system with data in a similar amount and variance of data as your production system has. If production has 20 million users, your test system must have the same number too! Use benerator to extract and anonymize production data or generate synthetic data!

Deletions:
Provide your system with data in a similar amount and variance of data as your production system has. If production has 20 million users, your test system must have the same number too! Use benerator to extract and anonymize production data or generate synthetic data!



Edited on 2010-11-29 12:20:59 by Admin

Additions:
1. Use test hardware that resembles production
2. Organize test data that resembles production data
3. Create user load and concurrency with production characteristics


Deletions:
1. Use test hardware that resembles production
2. Organize test data that resembles production data
3. Create user load and concurrency with production characteristics




Edited on 2010-11-29 12:20:22 by Admin

Additions:




Oldest known version of this page was edited on 2010-11-29 12:20:03 by Admin []
Page view:

3 Fundamentals Rules of Performance Testing


The three fundamental rules of performance testing
Violating any of these rules will make performance test results worthless for the prediction of production performance:
1. Use test hardware that resembles production
Performance is the result of dynamic interaction of systems with different roles and strengths. Having one component significantly different from production has ahigh risk of shifting performance characteristics! So rent or buy hardware similar to the production system for getting realistic behaviour!
2. Organize test data that resembles production data
Provide your system with data in a similar amount and variance of data as your production system has. If production has 20 million users, your test system must have the same number too! Use benerator to extract and anonymize production data or generate synthetic data!
3. Create user load and concurrency with production characteristics
Simulate a realistic number of concurrent users and applications that. LoadRunner, JMeter and Grinder can be used for this!
Page History :: 2010-11-29 12:22:05 XML :: Owner: Admin :: Search:
Valid XHTML 1.0 Transitional :: Valid CSS :: Powered by Wikka Wakka Wiki 1.1.6.0
Page was generated in 0.0219 seconds