The overwhelming majority of dynamic internet-facing applications are built on garbage collected runtimes such as Java and .NET. Garbage collection is popular because it promotes rapid application development. On the other hand, whenever a system is demonstrating unexpectedly poor performance, the garbage collector invariably surfaces as a possible suspect. Our advanced server analysis module even hooks into garbage collection performance monitoring on the .NET platform. The reality, however, is that modern garbage collectors are very good. Fact: Our company has been in business since 1999. In this time, no one can recall ever encountering a system with a performance problem that could … Continue reading »
The Web Performance load engine is the software Load Tester uses to create virtual users and generate load on the target. As with Load Tester, the load engine is a Java-based application that runs on its own Java virtual machine, which is included in the installation. There are two places the load engine is used: the local engine, which is included with Load Tester and runs inside the Load Tester JVM; and the remote engine, which is a standalone installation with its own JVM. The local engine is limited and intended mainly for replays and small tests, so in this … Continue reading »
My first day at Velocity was long, but fun. I breathed a sigh of relief when my luggage finally arrived…10 hours after I did. I attended part of a Load Testing workshop early in the afternoon that raised some interesting topics: Why are steady ramps bad? They showed some examples of how this approach can result in the wrong conclusions about system capacity. I agreed heartily – I’ve blogged on the merits of a stepped ramp in load tests previously. Abandonment rates – This is a feature that I’d like to get into Load Tester sooner rather than later. A … Continue reading »
We are getting close enough to the 3.6 release that I’m able to talk more about the new features – so look for more posts in the next few days. I blogged previously about the improved performance goal features, but at the time, I could not detail how they would be used to improve Load Tester’s analysis reports. The ability to set global page and transaction goals and override them individually for each page or transaction is a nice feature, as is the appearance of the goals on the performance charts. But the real value comes from Load Tester automatically … Continue reading »
Part 2: Performance and Distinct Error Handling under Computational Load In this report the same tests as part one are re-run, this time with no memory limitation showing a marked increase in Tomcat performance on Linux over Windows. Read the report ChrisWhen his dad brought home a Commodore PET computer, Chris was drawn into computers. 7 years later, after finishing his degree in Computer and Electrical Engineering at Purdue University, he found himself writing software for industrial control systems. His first foray into testing software resulted in an innovative control system for testing lubricants in automotive engines. … Continue reading »
Part 1: Performance and Distinct Error Handling under Memory Load This first part of this article measures performance information in order to distinguish the differences evident between the Windows® and Linux platforms. We find that given comparable hardware the performance differences introduced are almost trivial. When the server was pressed to capacity, our Windows installation was forced turn away some traffic with minimal alteration in serviced performance, whereas our Linux installation elected to service nearly all connections at the cost of introducing latency. However, prior to reaching capacity, our Linux server appeared on average to be capable of servicing connections at … Continue reading »
Durham, N.C. (PRWEB) – Web Performance, Inc. announces the release of two articles describing how the performance of the popular open source application server Tomcat differs on Windows and Linux. Apache Tomcat is a the official reference implementation of Java Servlet and JavaServer Pages, both specifications developed by Sun Microsystems under the Java Community Process. Apache Tomcat powers numerous large-scale, mission-critical web applications across a diverse range of industries and organizations. Users include such well-known companies such as WalMart and The Weather Channel. Sun’s release of their J2EE specifications has been followed by enthusiastic developers crafting powerful applications which can be seen … Continue reading »
Comparing The Performance of J2EE Servers The standardization of the application server, thanks to Sun’s J2EE specifications, has spawned a wealth of implementations. There are offerings from big players such as Sun, IBM, BEA and Oracle as well as numerous offerings from low-cost vendors and the open-source community. Like most developers, I participate in a number of technical forums and mailing lists. A recurring topic on servlet-development forums is “Which J2EE server should I use for my servlet-based application?” There are a number of criteria for selecting a server: ease of installation, quality of documentation, reliability, cost and performance. Some of … Continue reading »