Apache JMeter vs. Catchpoint

JMeter is well suited for Java applications where the user can script the scenario once and make changes to accommodate for as many numbers of users for load test execution. The image and selection of any files or exporting files scenario is handled well.

It is less appropriate to test Ajax applications where it is required to script click per use.

Incentivized

Proactive Website and API performance testing, Synthetic monitoring, and third-party integration are where Catchpoint is best suited. Catchpoint is less appropriate in Deep Application Performance monitoring, debugging complex user journeys in real-time, Small businesses, and Mobile app performance monitoring. These are the scenarios where I find Catchpoint is well-suited and scenarios where it is less appropriate.

Incentivized

• Easy of use - in generate load like HTTP requests, and processing/analyzing the responses. No coding is necessary at the basic level, just need to understand load testing and the infrastructure being tested.
• Automatic management of things like cookies to help with session state support - so you don't specifically have to worry about it or handle it
• Lots of testing/configuration options to suit your needs in making the right load generation (sampling requests), and analyzing the results, including any pre and post processing of the results first. Things like the Beanshell/BSF pre/post processors, response assertion, regular expression extractor, XPath extractor, CSV data set config
• There is a JMeter cloud service called BlazeMeter that I think would be useful for those that need to scale up high load without provisioning their own systems. I've not personally tried it though, but I recently attended a meetup presentation that highlighted nice useful features that BlazeMeter provides. One should evaluate the service if they are considering JMeter and need to expand beyond existing hardware resources.

• Catchpoint Synthetics: We create our synthetic monitoring using catchpoint. Creating the synthetics monitors are easy and requires basic knowledge on selenium and javascript. It allows you to run the test from external(backbone) and internal enterprise nodes. The screenshot and filmstrip feature is an add-on along with various customisations. Once created, It provides a detailed insight of each request that is involved in the application flow which helps us in addressing the issue at the request level.
• Catchpoint API Test: This is another kind of test which we have explored in our organisation. This has helped us to maintain the health check of our APIs and also we have utilised it for a variety of our use cases.
• Catchpoint Dashboard: This is our one-stop shop for all our monitors. It has multiple widgets that displays various application performance metrics. We use this feature immensely and it is of great value to the business.
• Catchpoint UI: It is very user friendly and with basic introduction anyone can just get started with it.

Incentivized

• Jmeter requires many tweaks with respect to its configuration file and thread properties. users need to edit theses files themselves. There could be some interface where we can edit this fields.
• Jmeter cannot handle more threads and hangs up when we increase the number of threads. This causes lot of inconvenience. In these situations, user can be notified that such change would be lead to slow performance so that user can do as required. The same appears when we try to view huge files on graph listener.
• Jmeter should optimize the read and write access to output csv since it acts as overhead to the I/O performance. This affects our test results for the application which we are testing.

• The ability to monitor the Catchpoint nodes with the ability to setup a take a recovery action based on specific criteria
• The ability to tell us when we are at X% capacity so that we better plan or budget for increasing the "capacity" of the Catchpoint nodes before we get to an overloaded state. The capacity utilization graph is not a reliable indicator for this metric. How can the capacity utilization rate get above 100%, it does not make sense

Incentivized

Price, Wiki and user sharing. Having access to the information provided by the developers and other open source providers is key for me. The ability to share information and get answers directly is very important to success in software testing. And the price of this product currently is amazing. Too many companies charge way too much money for products that are far behind in their value and pertinence

we are heavily dependent catchpoint system for the following functions * Detect end-user availability/performance-related problems * Ensures
service level objectives (SLO) are met, that prevents service level
agreement (SLA) breaches * Identify and understand the cause of any
network connectivity or application level issue * Improves the
availability and response time service levels

Incentivized

I can jump right into a new test plan and start building from scratch. The natural progression from test plan to thread group and then designing the basic format of the process is very streamlined and smooth. With only slight modifications I can build out a very complex model from a very basic beginning.

It's hard to find the functionalities that I am looking for in the application. Even if I did something in the past, after a time I have to re-learn again where the functionalities are. This is a powerful tool, but not user-friendly. Texts in the buttons and menus are not always meaningful or easily comprehensible.

Incentivized

I have been using JMeter for the last year. By using this tool, you can make sure the system will work under varied loads. It helps us to simulate real time scenarios by creating required virtual users and make sure the application will work under load. Perform load, stress, and stability testing using JMeter.

Incentivized

The customer support is fantastic as they keep you updated and follow up even though we may not even follow up. Make sure they send a communication so that we remain updated. They value engineers who will get on a call with you to understand any requirement we have on any test, and they bring in the best developers on call.

Incentivized

very easy to implement as the product is user-friendly

Incentivized

I have used LoadRunner and Silkperformer, and so far Jmeter turns out be the easiest to use of all these. While each of them have their own ROI, Jmeter can be picked by anyone in hours and start testing within a day. While with other tools, we need to get license, install them (takes a while) and setup tests and firewalls, etc.

Smart Bear Foglight Dynatrace CEM Catchpoint: I have used many synthetic monitoring products. Honestly, there are no big differences in features among all the products listed above or that I have used before. Probably, price and support might play big roles in selecting the products. I do not know the prices of these products.

Incentivized

• Good ROI on improving the performance of the application.
• Finding issues in the performance.
• Benchmark the performance results.
• CON: Need skillset to create and maintain the scripts in Java.
• Scripts are reusable and it is executed by any user.
• Need Client and Server setup to execute the scripts.

Incentivized

• The ROI has been very good with this product, we have seen multiple folds of time-saving by using this tool and preempting any risk associated with non-performant times of our server, hence increasing the team's capability to respond to certain downtime scenarios and the level of action that needs to be taken.
• Catchpoint’s observability solution makes it easier to have global visibility of our website's performance and to fix issues quicker
• I don't have any negatives, every good product comes with a cost, that is the fact but the Catchpoint tool has ultimately improved our ROI much beyond the changes that we pay

Incentivized