Dotcom-Monitor
Dotcom-Monitor has been monitoring the performance and uptime of websites for over 15 years. During that time we recognized that many of the monitoring scripts we used to monitor website transactions and to emulate real users on a website would be useful during load testing and stress testing as well. LoadView was built from the understanding that those teams that monitor a website for uptime and availability may also be interested in knowing the capacity of their websites and even testing the limits of the website infrastructure.
- +1 (888) 479-0741
- sales@loadview-testing.com
- 5125 County Road
101 Suite 100
Minnetonka, MN 55345
United States
Filter Results By:
Products
Applications
-
product
API Testing with LoadView
Simulate 1,000s of users hitting your API every second to generate 100,000+ calls to your server per load testing session.Define your API tests to simulate traffic at the pace you need by implementing a load curve that increases the number of simultaneous users as necessary to properly test your system.Gather performance metrics consisting of the response times of each session and validation that the API returns the expected results in each response.Visualize how the average response time is affected as you increase the number of simultaneous users.Examine individual test sessions to see error codes and utilize additional troubleshooting tools such as traceroutes, waterfall charts and a copy of the server response.
-
product
Cloud Based Scalability Testing
Perform load and stress tests on your system using a scalable cloud based platform. Get results on demand and ensure that your infrastructure scales.
-
product
Concurrent User Testing with LoadView
Concurrent user testing is also called simultaneous user testing. The idea behind concurrent user testing is to identify the response time of a website for a specified number of simultaneous users making requests to a website. Concurrent user testing measures how long it takes the server to respond to a specified number of simultaneous requests. A concurrent user test is often used to identify bottlenecks in the performance of a website- basically to find out how many simultaneous users can make requests of a website until the performance of the site is significantly degraded.
-
product
Load Testing vs. Stress Testing
A load test is a planned test to perform a specified number of requests to a system in order to test the functionality of the system under specific levels of simultaneous requests. A load test ensures that a web system is capable of handling an expected volume of traffic, and therefore is sometimes referred to as volume testing. The goal of a load test is to prove that a system can handle the expected volume with minimal to acceptable performance degradation. The threshold of acceptable performance degradation must be defined by the testers as some value considered acceptable to the end user so that users will not bounce from the site.
-
product
Performance Testing Tools from LoadView
Establish response time baselines under specific user load numbersIdentify performance bottlenecks as the number of simultaneous users increasesFind upper limits of current systems to plan for future capacity (Capacity Planning)Stress your production environment to see how and when things fail
