Skip to main content

Through LoadRunner Windows Resource Monitoring and Check Memory Leak

Windows Resource Monitoring

The Windows Resources monitor shows the Windows resources measured
during the scenario. Windows measurements correspond to the built-in
counters available from the Windows Performance Monitor.
Note: To monitor a Windows machine over a firewall, use TCP, port .
This chapter includes:
➤ Setting up the Monitoring Environment on page 
➤ Adding a Machine to Monitor on page 
➤ Configuring the Windows Resources Monitor on page 
➤ Windows Resource Performance Counters on page 

Setting up the Monitoring Environment
➤ If you are using the SiteScope monitor engine, ensure that SiteScope has
been installed on a server. You can install SiteScope on the same server as
the Controller, or on a dedicated server.
➤ If you want to monitor a remote Windows server that does not use Windows
domain security, you must authenticate the Controller on the remote
Windows server. To authenticate the Controller, create an account, or
change the password of the account used to log on to the Controller so that
it matches the password and user name used to log on to the remote
monitored Windows machine. When the remote Windows machine
requests another machine’s resources, it sends the logged-in user name and
password of the machine requesting the resources.
Adding a Machine to Monitor
In order to monitor the Windows resources of a particular machine from the
Controller, you need to add the machine and the measurements that you
want to monitor.
To add a machine to the Controller:
1 Click the Windows Resources graph in the graph tree, and drag it into the
right pane of the Run view.
2 Right-click the graph and select Add Measurements, or click anywhere on
the graph and choose Monitors > Add Measurements. The Windows
Resources dialog box opens.
3 By default, LoadRunner monitors Windows resources using the native
LoadRunner monitor engine.
If you want to monitor Windows resources using the SiteScope monitor
engine, click Advanced.
In the Choose Monitor Engine dialog box, choose SiteScope, and click OK
to close the Monitor Engine dialog box.

4 In the Monitored Server Machines section, click Add.
The Add Machine dialog box opens.
➤ In the Monitored Machine Information section, enter the server name or
IP address of the machine you want to monitor. Select the platform on
which the machine runs.
➤ In the SiteScope Server Information section, enter the SiteScope machine
name, and port (default: 8888), and specify whether you are using a
Secure HTTP connection. If you are using a SiteScope account, fill in the
relevant account information.
Note: If you are adding a native LoadRunner monitor, the SiteScope
Server Information section does not appear.
Click OK to close the Add Machine dialog box.
5 Click Add in the Resource Measurements on: <machine> section of the
Windows Resources dialog box.
6 Continue with “Configuring the Windows Resources Monitor” on page .
Configuring the Windows Resources Monitor
The configuration for this monitor differs slightly depending on whether
you are adding a native LoadRunner or SiteScope monitor.
This section describes:
➤ Configuring the Native LoadRunner Windows Resources Monitor
➤ Configuring the SiteScope Windows Resources Monitor
Configuring the Native LoadRunner Windows Resources
Monitor
1 When you add a machine in the Windows Resources dialog box, the default
measurements are displayed in the Resource Measurements on: <machine>
section.

Note: To change the default counters for the Windows machine monitor,
see “Changing a Monitor’s Default Counters” .
➤ To delete a measurement from the default list, select the measurement
and click Delete.
➤ To select additional measurements, click Add.
2 A Windows Resources dialog box opens displaying the available Windows
resources.
For each measurement select an object, counter, and instance, as described
in “Understanding the Add Windows Resources Measurements Dialog Box”, and then click Add.
For a description of the available measurements, see “Windows Resource
Performance Counters” 
3 When you have finished selecting the measurements to monitor, click
Close. The counters that you selected appear in the Resource Measurements
on: <machine> section of the Windows Resources dialog box.
4 Click OK in the Windows Resources dialog box to activate the monitor.
Configuring the SiteScope Windows Resources Monitor
The first time you add measurements you need to configure the remote
machine properties. When you click Add in the Resource Measurements on:
<machine> section of the Windows Resources dialog box, the Configuring
NT Remote Machine dialog box opens.
To configure a SiteScope Windows Resources monitor:
1 Enter the remote machine’s configuration information, as described in
“Understanding the Configuring NT Remote Machine Dialog Box” , and click OK.
2 The Configuring PDH Monitor dialog box opens. Verify the Server and
Update every properties, and click OK.
3 The Add Windows Resources Measurements dialog box opens displaying the
available measurements and server properties.













For each measurement select an object, measurement, and instance, as
described in “Understanding the Add Windows Resources Measurements
Dialog Box” on page 68, and then click Add.
For a description of the available measurements, see “Windows Resource
Performance Counters” .
Note: To change the default counters for the Windows machine monitor,
see “Changing a Monitor’s Default Counters” on page 395.
4 When you have finished selecting the measurements to monitor, click
Close. The measurements that you selected appear in the Resource
Measurements on: <machine> section of the Windows Resources dialog box.
5 Click OK in the Windows Resources dialog box to activate the monitor.
Understanding the Add Windows Resources
Measurements Dialog Box
The Add Windows Resources Measurements dialog box lets you select the
Windows resources to monitor. The Windows resources correspond to the
built-in counters available from the Windows Performance Monitor.
➤ Object. Select the object to monitor on the specified Windows machine.
➤ Counters/Measurements. Select the resource counter/measurement to
monitor. Select multiple counters using the CTRL key. For an explanation of
each counter, click Explain.
➤ Instances. If multiple instances of the selected counter are running, select
one or more instances to monitor for the selected counter.
➤ Explain. Displays a description of the selected counter.







Comments

Popular posts from this blog

Steps To Hunt the Bugs Successfully

The testers should catch the bugs in software that they’re testing. Testers should try to catch as several vital bugs as soon as possible. Catching the crucial bug earlier on Product-Life-Cycle can save the Projects from financial losses & mitigate the risks as compared for catching the same at a later stage in SDLC. Steps to hunt the bugs: Sometimes it’s useful to break the rules: The following test cases, which were predefined a tester can miss the bugs so it makes it impossible’s to provide the product i.e. 100 percent bug free. If you-follow pre-determined test cases you risks becoming blind to outside the bugs. A first secret is to check the functionality under the test. It’ll be an effective channel to discover the more bugs, because functionality is not generally covered by the test cases. Examine the patterns: You might have noticed that the bugs can be often met in the groups, one can call them-gregarious. The testing a new but the similar functionality...

Cross browser testing Tools

Cross Browser testing It is a process to test the web apps across multiple browsers. It involves the checking compatibility of the app across multiple web browsers & ensures that your web app’s works correctly across different web browsers. Tools for Cross Browser Testing Browser shots: The browser shots might be most exhaustive cross browser-testing tool that exists. Browser Shots includes all of most popular-browsers, like Firefox, Chrome, & Safari, along with the tons of another browser’s that might sound unfamiliar, like Sea Monkey, Flock, & Iceape. You can adjust the resolution, color-settings, & even Flash and JavaScript settings. Cross Browser Testing: It allows users to test their websites with over the hundred resolution or browser and Operating System combinations. This also has support to mobile web-browsers, which is crucial because the web traffic is making shift from the primarily desktop computer users to primarily mobile ...

Mobile Application Testing: Strategy for Development

There are a huge number of demands and lots of competitions in the mobile application industries. In that demands and competitions, the mobile application testing has become more important. The testing phase of the mobile application testing looks like evil between the creative process and excitement of new products in the market. According to the survey, “In US, on an average 2-3 hours per day people spends their time on smartphones and tablets. On that time, they spent 80% on mobile application and remaining 20% on web applications.” Few list of key factors for successful mobile application testing strategies are: Selection of Device for Testing : Before introducing the mobile application test activities, first select the devices for testing the application. Selection decision is very important because only devices can help to targets maximum numbers of the customers for accessing the application. There are two parts for device selection: §   Device Model ...