PERFORMANCE :: Module 01 :: Lesson 1 :: Topic 2 :: Environment Set up and Prerequisites
This article is a part of the Self-paced Learning Series for the Course: First-Hand Experience of eureQa.Please refer to the link for more details on the Course.
Introduction of Worksoft Feature/Concept :: Lesson 1 :: Topic 2
Every test must or will have a set of criteria/measurement that is to be considered which is either constant or changing. As for many factors that influence a test, for performance it is important we consider the environment we execute and other subfactors of this. Generally said, Execute perf in test environments that are as close to the production systems as possible. Because Perf is done for Real time testing intended to give results as realistic as possible to the actual usage than simulations.
When we talk about environment, we also consider, the access, generally public but rarely private and both might require whitelisting of a certain IP addresses. And also how does the test gets influenced by server locations vs user usage locations. Here, we discuss on Latency & Rate Throttling
Latency – The time taken for a packet to be transferred across a network.
In terms of performance optimization, it's important to optimize to reduce causes of latency and to test site performance emulating high latency to optimize for users with lousy connections.
Latency is affected by several factors: distance, propagation delay, internet connection type, website content, Wi-Fi, and your router. Some of these factors are fixable, while others are just part of everyone's online experience.
Network rate limiting - It is used to limit the amount of traffic on a network.Rate limiting refers to preventing the frequency of an operation from exceeding some constraint. In large-scale systems, rate limiting is commonly used to protect underlying services and resources.When we are executing tests of a certain frequency it is mandate to check for any such constraints of rate limiting and ensure that the IP address ranges are whitelisted at customer environement to ensure continuity of tests.
Cache is another factor that influences the performance metrics. Browser or Server. Manual comparison of testing or capturing performance metrics for individual users of different network configs are not recommended for comparison. While server cache can be. And sometimes, we also need to warm up our newly configured environments before we execute the actual tests so that we reduce the latency. A warm-up period is necessary to make sure that the state of server resources, such as memory or cache, is prepared for the normal operating mode.
When we talk about environment, we also consider, the access, generally public but rarely private and both might require whitelisting of a certain IP addresses. And also how does the test gets influenced by server locations vs user usage locations. Here, we discuss on Latency & Rate Throttling
Latency – The time taken for a packet to be transferred across a network.
In terms of performance optimization, it's important to optimize to reduce causes of latency and to test site performance emulating high latency to optimize for users with lousy connections.
Latency is affected by several factors: distance, propagation delay, internet connection type, website content, Wi-Fi, and your router. Some of these factors are fixable, while others are just part of everyone's online experience.
Network rate limiting - It is used to limit the amount of traffic on a network.Rate limiting refers to preventing the frequency of an operation from exceeding some constraint. In large-scale systems, rate limiting is commonly used to protect underlying services and resources.When we are executing tests of a certain frequency it is mandate to check for any such constraints of rate limiting and ensure that the IP address ranges are whitelisted at customer environement to ensure continuity of tests.
Cache is another factor that influences the performance metrics. Browser or Server. Manual comparison of testing or capturing performance metrics for individual users of different network configs are not recommended for comparison. While server cache can be. And sometimes, we also need to warm up our newly configured environments before we execute the actual tests so that we reduce the latency. A warm-up period is necessary to make sure that the state of server resources, such as memory or cache, is prepared for the normal operating mode.