Skip to main content

Posts

How to troubleshoot high CPU utilization during performance testing

When troubleshooting high CPU utilization during performance testing, it is important to identify the root cause of the issue. Here are some steps you can take to troubleshoot and address high CPU utilization: Monitor System Resources: Use performance monitoring tools to track CPU usage over time. Monitor other system resources such as memory, disk I/O, and network usage to understand if any of these factors are contributing to high CPU utilization. Identify CPU-Intensive Processes: Identify the specific processes or components that are consuming a significant amount of CPU resources. Performance monitoring tools can help you pinpoint the culprits. Look for any particular application, service, or module that stands out in terms of CPU usage. Analyze Code and Algorithms: If your application has custom code or algorithms, review them for any inefficiencies or performance bottlenecks. Look for areas where CPU-intensive operations are performed frequently or where large amounts of data are...

What is Performance Testing - Advanced Level

For advanced testers, performance testing goes beyond the basic validation of response times and throughput. It involves a more comprehensive and detailed approach to evaluate system performance under various conditions.  Here are some aspects of performance testing that advanced testers typically focus on: Performance Test Planning: Advanced testers excel in creating well-defined performance test plans. They analyze the application architecture, identify critical scenarios, determine performance goals, and select appropriate performance testing techniques and tools. Performance Test Design: Advanced testers design complex and realistic performance test scenarios that accurately mimic real-world usage patterns. They incorporate various factors like user profiles, data volumes, transaction mix, and think creatively to cover different testing objectives. Performance Test Execution: Advanced testers execute performance tests with precision and accuracy. They monitor system resource...

Key performance metrics to monitor

  In performance testing, various key metrics are measured to evaluate the behavior and effectiveness of a system under different loads. The selection of specific metrics may vary depending on the type of application and its intended use. Here are some commonly used performance metrics: Response Time: The time taken for the system to respond to a user request. It includes the server processing time, network latency, and client-side rendering time. Throughput: The number of transactions or requests processed by the system within a given time frame. It indicates the system's capacity to handle concurrent user requests. Concurrent Users: The number of simultaneous users or connections the system can support without significant degradation in performance. Error Rate: The percentage of failed or erroneous transactions or requests compared to the total number of transactions. It helps identify system stability and reliability. CPU Usage: The percentage of CPU resources utilized by th...

String Comparison in Loadrunner script

How to compare a string in Loadrunner script? -There are various methods to compare a string, in below example we have used "strcmp" to compare two values. We have captured a string in "pComparisonString" parameter and comparing it with ABC. Lets say if you have captured some string using correlation and want to compare if the captured string meets the condition then only pass the transactions else fail the transaction: if (strcmp(lr_eval_string("{pComparisonString}"),"ABC") == 0) { lr_output_message("The parameter value is %s", lr_eval_string("{pComparisonString}")); lr_end_transaction("Transaction_Failed",LR_FAIL); } else { lr_error_message("No parameter value captured."); lr_end_transaction("Transaction_Passed",LR_PASS); } -------------------------------------------------------- strcmp- String comparison function. pComparisonString- String which we have captured for compar...

What is Performance Testing and why it is important?

We spend most of our time by browsing Facebook, watching videos, uploading photos and many other online activities. Have you ever noticed if you are watching a video and all of sudden the website goes down? If you are trying to book an online ticket and on the payment page, the website stops responding? If you are adding the last available item on sale in the shopping cart and the website gets hung? Isn't it stressful? For every growing business, it's very crucial to keep a tap on the performance of their application. If a website takes more than 2 seconds to respond then users tend to move to some other website which can cause a huge business loss.  Let's say you are on a retail website and browsing for some item that takes around 2-3 seconds to respond to each click or loading the page. In most cases, the user will go for some other website. Performance Testing gives an idea about how the system is going to behave on load and can help the business owners to ...

What is Pacing and how it's different from the Think Time

Pacing is the time that will hold/pause the script before it goes to the next iteration. i.e Once the Action iteration is completed the script will wait for the specific time(pacing time) before it starts the next one. It works between two actions. eg, if we record a script there will be three default actions generated by the Load Runner: vuser_init, Action, and vuser_end, the pacing will work after the Action block and hold the script before it goes to repeat it. The default blocks generated by LoadRunner is shown below: Actions marked in Red Think Time: It replicates the real-time user behavior by adding a delay between two actions/transactions.  In one of the interviews, I was asked if we give think time at the end of the script it will also work as Pacing then why HP has given two different parameters for the same purpose. Each of them has a different purpose: Think Time will keep the thread active and LoadRunner will expect for another transaction, however, in pacing t...

Auto Correlation issue in VUGen 12

The auto correlation rule in VUGen 12 sometime fails to capture the values due to maximum length limit. You can increase the maximum length by: Increase the length of ‘MaxParamLen=4096’ to 99999 in ‘correlationsettings.xml’ file in \\vuGen\config folder. Save the changes and restart the VUGen, the auto correlation rule will capture the data.