Welcome!

Weblogic Authors: Yeshim Deniz, Elizabeth White, Michael Meiner, Michael Bushong, Avi Rosenthal

Related Topics: Weblogic, Java IoT

Weblogic: Article

Approaches to Performance Testing

A best-practices approach to maximize your performance test effort

Now comes the part where you actually run your capacity-planning test. The next question is, "How do I load the users to simulate the load?" The best way to do this is to try to emulate how users hit the server during peak hours. Does that user load happen gradually over a period of time? If so, a ramp-up-style load should be used, where x number of users are added ever y seconds. Or, do all of the users hit the system in a very short period of time all at once? If that is the case, a flat run should be used, where all of the users are simultaneously loaded onto the server. These different styles will produce different results that are not comparable. For instance, if a ramp-up run (Figure 5) is done and you find out that the system can support 5,000 users with a response time of 4 seconds or less, and then you follow that test with a flat run with 5,000 users, you'll probably find that the average response time of the system with 5,000 users is higher than 4 seconds. This is an inherent inaccuracy in ramp-up runs that prevents them from pinpointing the exact number of concurrent users that a system can support. For a portal application, for example, this inaccuracy is amplified as the size of the portal grows and as the size of the cluster is increased.

This is not to say that ramp-up tests should not be used. Ramp-up runs are great if the load on the system is slowly increased over a long period of time. This is because the system will be able to continually adjust over time. If a fast ramp-up is used, the system will lag and artificially report a lower response time than what would be seen if a similar number of users were being loaded during a flat run. So, what is the best way to determine capacity? Taking the best of both load types and running a series of tests will yield the best results. For example, using a ramp-up run to determine the range of users that the system can support should be used first. Then, once that range has been determined, doing a series of flat runs at various concurrent user loads within that range can be used to more accurately determine the capacity of the system (Figure 6).

Soak Tests
A soak test is a straightforward type of performance test. Soak tests are long-duration tests with a static number of concurrent users that test the overall robustness of the system. These tests will show any performance degradations over time via memory leaks, increased garbage collection (GC), or other problems in the system. The longer the test, the more confidence in the system you will have. It is a good idea to run this test twice - once with a fairly moderate user load (but below capacity so that there is no execute queue - Figure 7), and once with a high user load (so that there is a positive execute queue - Figure 8).

These tests should be run for several days to really get a good idea of the long-term health of the application. Make sure that the application being tested is as close to real world as possible with a realistic user scenario (how the virtual users navigate through the application), testing all of the features of the application. Ensure that all the necessary monitoring tools are running so that problems will be accurately detected and tracked down later (Figure 9).

Peak-Rest Tests
Peak-rest tests are a hybrid of the capacity-planning ramp-up-style tests and soak tests. The goal here is to determine how well the system recovers from a high load (such as one during peak hours of the system), goes back to near idle, and then goes back up to peak load and back down again.

The best way to implement this test is to do a series of quick ramp-up tests followed by a plateau (determined by the business requirements), and then a dropping off of the load. A pause in the system should then be used, followed by another quick ramp-up - then you repeat the process. A couple of things can be determined from this: Does the system recover on the second "peak" and each subsequent peak to the same level (or greater) than the first peak? And does the system show any signs of memory or GC degradation over the course of the test? The longer this test is run (repeating the peak/idle cycle over and over), the better idea you'll have of what the long-term health of the system looks like.

Summary
This article has described several approaches to performance testing. Depending on the business requirements, development cycle, and life cycle of the application, some tests will be better suited than others for a given organization. In all cases though, you should ask some fundamental questions before going down one path or another. The answers to these questions will then determine how to best test the application. These questions are:

  • How repeatable do the results need to be?
  • How many times do you want to run and rerun these tests?
  • What stage of the development cycle are you in?
  • What are your business requirements?
  • What are your user requirements?
  • How long do you expect the live production system to stay up between maintenance downtimes?
  • What is the expected user load during an average business day?
By answering these questions and then seeing how the answers fit into the aforementioned performance test types, you should be able to come up with a solid plan for testing the overall performance of your application.

More Stories By Matt Maccaux

Matt Maccaux is a performance engineer on WebLogic Portal at BEA.

Comments (3) View Comments

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


Most Recent Comments
Deepak Batra 04/26/06 09:08:56 PM EDT

Great article by Matt. It definitely explains the process of WebLogic Performance Tuning & Testing well.

Arcturus (www.arcturustech.com) can help make the process of WebLogic Performance Tuning easy. AutoPilot WL, our flagship product completely automates WebLogic tuning process.

AutoPilot uses a wizard based approach, it takes a load script, generates load and monitors j2ee application & WebLogic's behavior (including transactions, WebLogic threads, ejbs, jms, jdbc, various pools and a lot more..). In the process, AutoPilot analyzes WebLogic & application's cumulative behavior after each run and makes appropriate adjustments to get the optimum performance. AutoPilot also automatically bounces WebLogic server as and when needed in the process. AutoPilot continues this process unless desired goals are achieved or certain user defined thresholds are reached. WebLogic tuning is in a way a misnomer, it is actually aligning WebLogic as per your application and environment's requirements. You can download an evaluation version of AutoPilot at the following url and try it for yourself.

http://support.arcturustech.com/downloadpage.do

You can get more details on WebLogic Performance Tuning Process using AutoPilot at the following URL.

http://support.arcturustech.com/AutoPilot_WL_Help/Tuning_Your_WebLogic_S...

It is recommended by Arcturus to use AutoPilot Advisor before tuning. Advisor analyzes complete application environment for any configuration related issues using its in built knowledge and gives recommendations. It is like attaching your WebLogic environment to a computer that runs a 1000 point inspection on it and either fixes issues or advises how to fix them. Advisor is a great way to find out where there is room for improvement even before you get into Performance Testing & Tuning. It even guides with the relevant BEA CRs that can save an outage situation. We recommend CRs based on their applicability (not blindly).

We also understand no matter how much effort one puts into an application, we are bound to find apllication/weblogic issues that cause WebLogic server to hang. AutoPilot Detector and Blackbox handle those situations and provide you with an instant root cause report. Feel free to drop me an email ([email protected]) if you any questions at all.

Deepak Batra 04/26/06 09:08:21 PM EDT

Great article by Matt. It definitely explains the process of WebLogic Performance Tuning & Testing well.

Arcturus (www.arcturustech.com) can help make the process of WebLogic Performance Tuning easy. AutoPilot WL, our flagship product completely automates WebLogic tuning process.

AutoPilot uses a wizard based approach, it takes a load script, generates load and monitors j2ee application & WebLogic's behavior (including transactions, WebLogic threads, ejbs, jms, jdbc, various pools and a lot more..). In the process, AutoPilot analyzes WebLogic & application's cumulative behavior after each run and makes appropriate adjustments to get the optimum performance. AutoPilot also automatically bounces WebLogic server as and when needed in the process. AutoPilot continues this process unless desired goals are achieved or certain user defined thresholds are reached. WebLogic tuning is in a way a misnomer, it is actually aligning WebLogic as per your application and environment's requirements. You can download an evaluation version of AutoPilot at the following url and try it for yourself.

http://support.arcturustech.com/downloadpage.do

You can get more details on WebLogic Performance Tuning Process using AutoPilot at the following URL.

http://support.arcturustech.com/AutoPilot_WL_Help/Tuning_Your_WebLogic_S...

It is recommended by Arcturus to use AutoPilot Advisor before tuning. Advisor analyzes complete application environment for any configuration related issues using its in built knowledge and gives recommendations. It is like attaching your WebLogic environment to a computer that runs a 1000 point inspection on it and either fixes issues or advises how to fix them. Advisor is a great way to find out where there is room for improvement even before you get into Performance Testing & Tuning. It even guides with the relevant BEA CRs that can save an outage situation. We recommend CRs based on their applicability (not blindly).

We also understand no matter how much effort one puts into an application, we are bound to find apllication/weblogic issues that cause WebLogic server to hang. AutoPilot Detector and Blackbox handle those situations and provide you with an instant root cause report. Feel free to drop me an email ([email protected]) if you any questions at all.

news desk 02/18/06 03:08:31 PM EST

Performance testing a J2EE application can be a daunting and seemingly confusing task if you don't approach it with the proper plan in place. As with any software development process, you must gather requirements, understand the business needs, and lay out a formal schedule well in advance of the actual testing.

IoT & Smart Cities Stories
The challenges of aggregating data from consumer-oriented devices, such as wearable technologies and smart thermostats, are fairly well-understood. However, there are a new set of challenges for IoT devices that generate megabytes or gigabytes of data per second. Certainly, the infrastructure will have to change, as those volumes of data will likely overwhelm the available bandwidth for aggregating the data into a central repository. Ochandarena discusses a whole new way to think about your next...
DXWorldEXPO LLC announced today that Big Data Federation to Exhibit at the 22nd International CloudEXPO, colocated with DevOpsSUMMIT and DXWorldEXPO, November 12-13, 2018 in New York City. Big Data Federation, Inc. develops and applies artificial intelligence to predict financial and economic events that matter. The company uncovers patterns and precise drivers of performance and outcomes with the aid of machine-learning algorithms, big data, and fundamental analysis. Their products are deployed...
Dynatrace is an application performance management software company with products for the information technology departments and digital business owners of medium and large businesses. Building the Future of Monitoring with Artificial Intelligence. Today we can collect lots and lots of performance data. We build beautiful dashboards and even have fancy query languages to access and transform the data. Still performance data is a secret language only a couple of people understand. The more busine...
All in Mobile is a place where we continually maximize their impact by fostering understanding, empathy, insights, creativity and joy. They believe that a truly useful and desirable mobile app doesn't need the brightest idea or the most advanced technology. A great product begins with understanding people. It's easy to think that customers will love your app, but can you justify it? They make sure your final app is something that users truly want and need. The only way to do this is by ...
CloudEXPO | DevOpsSUMMIT | DXWorldEXPO are the world's most influential, independent events where Cloud Computing was coined and where technology buyers and vendors meet to experience and discuss the big picture of Digital Transformation and all of the strategies, tactics, and tools they need to realize their goals. Sponsors of DXWorldEXPO | CloudEXPO benefit from unmatched branding, profile building and lead generation opportunities.
Digital Transformation and Disruption, Amazon Style - What You Can Learn. Chris Kocher is a co-founder of Grey Heron, a management and strategic marketing consulting firm. He has 25+ years in both strategic and hands-on operating experience helping executives and investors build revenues and shareholder value. He has consulted with over 130 companies on innovating with new business models, product strategies and monetization. Chris has held management positions at HP and Symantec in addition to ...
Cell networks have the advantage of long-range communications, reaching an estimated 90% of the world. But cell networks such as 2G, 3G and LTE consume lots of power and were designed for connecting people. They are not optimized for low- or battery-powered devices or for IoT applications with infrequently transmitted data. Cell IoT modules that support narrow-band IoT and 4G cell networks will enable cell connectivity, device management, and app enablement for low-power wide-area network IoT. B...
The hierarchical architecture that distributes "compute" within the network specially at the edge can enable new services by harnessing emerging technologies. But Edge-Compute comes at increased cost that needs to be managed and potentially augmented by creative architecture solutions as there will always a catching-up with the capacity demands. Processing power in smartphones has enhanced YoY and there is increasingly spare compute capacity that can be potentially pooled. Uber has successfully ...
SYS-CON Events announced today that CrowdReviews.com has been named “Media Sponsor” of SYS-CON's 22nd International Cloud Expo, which will take place on June 5–7, 2018, at the Javits Center in New York City, NY. CrowdReviews.com is a transparent online platform for determining which products and services are the best based on the opinion of the crowd. The crowd consists of Internet users that have experienced products and services first-hand and have an interest in letting other potential buye...
When talking IoT we often focus on the devices, the sensors, the hardware itself. The new smart appliances, the new smart or self-driving cars (which are amalgamations of many ‘things'). When we are looking at the world of IoT, we should take a step back, look at the big picture. What value are these devices providing. IoT is not about the devices, its about the data consumed and generated. The devices are tools, mechanisms, conduits. This paper discusses the considerations when dealing with the...