Wednesday, August 28, 2013
What are different policies to prevent congestion at different layers?
Posted by
Sunflower
at
8/28/2013 10:09:00 PM
0
comments
Labels: Avoidance, Capacity, Congestion, Congestion control, Control, Efficiency, Layers, Network, Networking, Operation, Parameters, Path, Policies, Prevent, Prevention, Resources, Throughput, traffic, User
![]() | Subscribe by Email |
|
Tuesday, April 30, 2013
What is hard disk and what is its purpose?
Hard Disk and its Purpose
Posted by
Sunflower
at
4/30/2013 08:48:00 PM
0
comments
Labels: Access, Benefits, Capacity, Characteristics, Data, Discs, Disk Drive, Drives, files, Hard Disk Drives, HDD, Information, Operating System, Performance, Random, Read, Storage, Store, System, Write
![]() | Subscribe by Email |
|
Saturday, July 28, 2012
What is virtual user script? Why do you need to parametrize fields in your virtual user script?
What is a Virtual User?
What is a Virtual User Script & Need to Parametrize fields?
- Static
text
- Edit
text
- Pictures
- Icons
- User
items and so on.
- Select
- Drag
- Type
- Close
- Click
and so on.
Posted by
Sunflower
at
7/28/2012 10:52:00 PM
0
comments
Labels: Application, Behavior, Capacity, Fields, Functions, Load, Parameters, Parametrize, Scripts, Simulate, Software System, Statements, Stress, Tasks, Testing, Users, Virtual, Virtual Script, Virtual user, Website
![]() | Subscribe by Email |
|
Wednesday, January 4, 2012
What are different aspects of stress testing?
Stress testing can be defined as a form of testing that is carried out to determine the stability and the stress handling capacity of a software system or module. Stress testing is all about testing the software system or application beyond the normal operational capacities. It is the testing of software system or application to its breaking or fatal point. This is done in order to observe the results.
Stress testing has a much broader meaning. What is basically understood by a stress test?
- It is referred to a test that mainly focuses upon the availability, error handling and robustness of a software system or application.
- In stress testing the software system or application is subjected heavy loads of tasks.
- It is not about considering the proper behavior under the normal operational conditions or user environment.
Typically the goal of stress testing is to test whether or not the software system or application crashes or fails in the case of catastrophic problems like unavailability of sufficient computing resources. These computational resources may include disk space or memory. It is also done to determine if the system crashes or fails under the situation of denial of service attacks and unusually high concurrency.
Stress testing, load testing, volume testing all seem like much similar kinds of testing.
A look at the following examples of stress testing will clear up the confusions regarding stress testing:
- Stress testing for web server:
A web server can be subjected to stress testing using bots, scripts and several denial of service tools to determine its performance and behavior during the peak data and tasks load.
- Stress testing can be studied in contrast with load testing.
Load testing is basically carried out to examine the entire testing environment and the huge database. It is also carried out to determine the response time of the software system or application whereas the stress testing exclusively focuses upon identifying the transactions and pushing them to a level at which a break occurs in the execution of the transaction software system.
Another point is that during the stress testing if the transactions are duly stressed, then the chance is that the database may not experience a huge data load. However if the transactions are not stressed, the data base may experience a heavy work load.
SOME IMPORTANT POINTS:
- Stress testing is another word for system stress testing.
- It can be defined as the loading of the concurrent users beyond and over the level that can be handled by the system.
- This leads to the breakage of the weakest link in the whole software system or application.
- While carrying out the stress testing the software engineers, developers or testers need to test the whole software system or application under the desired expected stress as well as under the accelerated stress.
- The goal here is to determine the working life of the software system.
- It is also aimed at determining the modes of failure for the software system or application.
- For the hardware counterpart of a complete system, the stress testing can be defined as the subjecting of the concerned hardware to the exaggerated levels of stress.
- This is basically done to determine the stability of the hardware system when used in a normal environment rather than a testing environment.
- Before modifying the CPU parameters during the processes of over clocking, over volting, under volting and under clocking, it is necessary to verify whether or not the new CPU parameters like frequency and core voltage are suitable for taking the heavy CPU loads.
- Stress testing for such parameters is usually carried out by executing a CPU intensive program for a prolonged significant period of time. It is observed if the system crashes or hangs.
Posted by
Sunflower
at
1/04/2012 02:38:00 PM
0
comments
Labels: Application, Capacity, Crash, Focus areas, Goals, Load, Memory, Operational, Resources, Software testing, Stability, Stress, Stress testing, System Testing, Tasks, Tests, Users
![]() | Subscribe by Email |
|
Wednesday, January 5, 2011
Volume tests - Volume Testing of Messaging systems
Volume tests are often most appropriate to messaging, batch and conversion processing type situations. In a volume test, there is often no such measure as response time. Instead, there is usually a concept of throughput. A key to effective volume testing is the identification of the relevant capacity drivers. A capacity driver is something that directly impacts on the total processing capacity. For a messaging system, a capacity driver may well be the size of messages being processed.
Most messaging systems do not interrogate the body of the messages they are processing, so varying the content of the test messages may not impact the total message throughput capacity, but significantly changing the size of the messages may have a significant effect. However, the message header may include indicators that have a very significant impact on processing efficiency. For example, a flag saying that the message need not be delivered under certain circumstances is much easier to deal with than a message with a flag saying that it must be held for delivery for as long as necessary to deliver the message, and the message must not be lost. In the former example, the message may be held in memory, but in the later example, the message must be physically written to disk multiple times.
Before conducting a meaningful test on a messaging system, the following must be known:
- the capacity drivers for the messages.
- the peak rate of messages that need to be processed, grouped by capacity driver.
- the duration of peak message activity that needs to be replicated.
- the required message processing rates.
A test can then be designed to measure the throughput of a messaging system as well as the internal messaging system metrics while that throughput rate is being processed. Such measures would typically include CPU utilization and disk activity. It is important that a test be run, at peak load, for a period of time equal to or greater than the expected production duration of peak load.
Posted by
Sunflower
at
1/05/2011 02:48:00 PM
0
comments
Labels: Capacity, Duration, Header, Messages, Messaging System, Peak, Process, Response time, Software testing, Tests, Throughput, Time, Volume, Volume test, Volume testing
![]() | Subscribe by Email |
|