dmmckinn 1200006SCS Visits (936)
In continuing on the topic of Performance testing, Vaughn Rokosz takes a look at some of the common reasons performance tests can fail, and suggests ways of tuning your servers to avoid the common issues.
Take a look at his latest article that includes the following:
For your convenience, here is the link to the previous article on the subject: Creating a perf
dmmckinn 1200006SCS Visits (749)
Looking for information about how to build performance simulations?
Building a good simulation of a user population requires expertise at many levels, including:
In the following article Vaughn Rokosz, a technical lead for the CLM performance team, shares some of his experiences with building performance simulations of the Jazz products. He walks through a simple example demonstrating how to build a simulation of a user population that is creating work items in Rational Team Concert. He also shares some of the things used to make the development of performance simulations simpler by attaching the Rational Performance Tester project that he used when working through the example.
Stay tuned for part 2...
Rajeshavanthi 2700022MCX Visits (783)
You could see the 'Additional delay' under Client processing delay section for each request, under Advanced tab.
What happens if you make this delay to zero??
Does the play back show much difference in overall response time?
Generally, the time taken to load the entire page outside IBM Rational Performance Tester (RPT) cannot be mapped to the time taken to load the same page when invoked via RPT recorder. There are lot of parameters that RPT, as a load performance testing tool, accounts for (such as the traffic and connection information).
Also, RPT processes these Client side delays in parallel or sequentially depending on how the application server returns them. Sometimes if you try modifying/disabling the client processing delay value, it may also disable the immediate transaction under Rational Performance Tester. Because, practically speaking, when you disable a request, you potentially invalidate some delays because in theory the disabled request could have been the basis for a delay. Therefore, RPT automatically recalculates the delays on the page when you disable a request. That is, if a later request used the disabled one as a base, the later delay request should be adjusted.
Now, let's come to your question about why such discrepancy between the response in the browser and RPT...
Often times when you see response times that are inaccurate it is because of recording your actions too fast and so you end up with more than one page being combined together. When recording, you need to be mindful and make sure to pause between mouse clicks. Do an action and wait 5 seconds before continuing on to the next action. You also need to pay attention to where your mouse is and make sure you have no "hover gifs" that you accidentally cause to be sent to the server while recording.
To see if you have these problems you have two things you can look at.
1. Open the test and click on the name of the test under test Contents in the tree. Click Select->Request. On the right hand side you will see a table of all requests in your test. Look at the delay column and look for really large delay values. If you have these, they are usually caused by recording too quickly, and act as an "embedded" think on the page. The Client Delay is supposed to simulate how long your client took to process the data from the server before sending the next piece of data. When you record too quickly, these values can be skewed. You can also go to a specific page that is taking too long and look at those specific requests. You can use the same Select button, or you can go to the Advanced tab of each request and look at its delay.
2. If you find the delays are your problem, then you can split the page where the delays are long since this was probably supposed to be two pages. This will move that delay to be the think time of the page which would be more accurate. You can also go to Wind
Also remember that when doing recording, we will capture each connection that was used and will send out the requests on the same connection that they were sent on originally. If you had two connections sending requests at record time, we will send requests on two connections at execution time. If you see a really long client delay, then look at that request in detail to determine if it was something that was sent by a user gesture or as a result of the primary request.
vjagadeesh 2700063KJN Visits (798)
Rational Performance Tester supports the TN3270 protocol. However, the TN5250 protocol is still undergoing testing.
The recording of the application using TN5250 protocol is possible using the Socket protocol, as there is no specific protocol recorder provided for this. Identifying and debugging issues which arise during a re-run of the recorded test is difficult using the Socket protocol. Although it is not advisable to use the Socket protocol; there is no other option currently available to use Rational Performance Tester with applications using the TN5250 protocol.
PaulLiskay 06000284J3 Visits (961)
How to do a silent install of IBM Rational Performance Tester (RPT), or the RPT Load agent is a common topic. To do one on Linux is a bit trickier than on Microsoft Windows because most people are more familiar with Windows than Linux. Don't worry, it's still relatively easy and straight forward.
The approach I took was:
1. download IM 1.8.2 and the RPT 8.7 Agent repositories
2. copy from Windows machine to Linux machine using pscp, a Windows version of scp (secure copy)
3. install the standalone Installation Manager 1.8.2 for Linux
4. run that Installation Manager in GUI mode to create a response file needed for the silent install
5. then run Installation Manager from the command line using the response file generated in step 4 to install the agent silently.
Here's the steps
1. download IM 1.8.2 from htt
2. copy to Linux machine, I'm copying to /tmp/IM182
3. unzip on Linux machine to /tmp/IM182
[root@citmx373 IM182]# unzip age
4. install IM
[root@citmx373 IM182]# pwd
5. copy the agent to the Linux machine, I'm copying to /tmp/RPT87Agent
6. unzip it
[root@citmx373 RPT87Agent]# pwd
7. run IM in GUI mode to create a response file
[root@citmx373 eclipse]# pwd
8. Verify creation of response file
root@citmx373 eclipse]# ls /tmp
9. Do the silent install using the response file just created
[root@citmx373 eclipse]# pwd
10. Verify installation.
Check that the majordomo.config file exists and has the right hostname of the RPT workbench. Then check if the agent is started.
[root@citmx373 Majordomo]# pwd
11, Check agent status on RPT workbench by clicking on the agent status icon