Contact Us
LoadView Support Team
Dotcom-Monitor’s LoadView team offers unparalleled 24/7 support.
Our performance engineers are standing by to guide you through the setup, scripting, and testing process.
Contact Support
Info
2500 Shadywood Road Suite #820 Excelsior, MN 55331
+1 (888) 479-0741
sales@loadview-testing.com
Phone Numbers
Toll Free
1-888-479-0741
USA Local
+1-612-278-1943
United Kingdom
+44 2070431669
LoadView FAQs
How are VUs (Virtual Users) determined for a test?
Device calibration is performed to calculate the optimal Virtual User Distribution (VUD) value for the number of Virtual Users per load injector server. The device tasks, complexity, and required CPU resources are considered during calibration. Based on our experience, by default, we use the average VUD that is optimal to ensure ideal CPU utilization per load injector (up to 80%) and efficient virtual user distribution between load injectors. Calibrated Virtual User Distribution varies based on a task type:
HTTP/S Test – 8 to 500 users
Web Page/Web Application Test – 2 to 8 users
Web Application with Rich Internet Application (RIA) image validation – 2 to 5 users
Why is calibration for load testing HTTP URL and web applications different?
When will I be billed?
What is the maximum number of users can you generate?
There is virtually no limit to the number of users that can be generated for a load test since LoadView runs in the cloud. The tests are theoretically limited by the total number of load injectors available from the cloud providers at any given point and by the cost to lease those servers from cloud providers. Given enough advanced time to setup a test, you should be able to generate as much load as you need to complete a proper load test.
Why do I need to calibrate my test before getting the exact pricing?
Calibrating a test automatically determines how much CPU percentage is used by the load injector for each simultaneous user. This tells us how many simultaneous users we can run per load injector. The number of load injector directly affects the cost of the test.
When should I use protocol, headless browser, or real browser-based tests?
Depending on the specific need, use case, or technology of the system being tested, the LoadView platform can be utilized to run multiple user simulation types – HTTP/S, headless browser-based, and real browser-based simulations.
- HTTP/S-based load simulation
Protocol level scripts are perfect for component level tests in CI/CD environments and have a low footprint on load injection machines. Recommended for testing the following:
• Web servers
• Web APIs, such as JSON, SOAP, Rest, and XML
• Single web pages without JavaScript or CSS
- Headless browser-based simulation
Often faster than real browsers since you bypass all the elements of a real browser like JavaScript, CSS, and HTML, headless browsers are great for automating tasks and instances where you’re looking to get browser data quickly. Headless browser-based simulation has a medium footprint on load injection machines.
- Real browser-based simulation
When you need to simulate real user behavior and have web applications that utilize specific technologies and Rich Internet Applications (RIA), like JavaScript, CSS, Flash, or AJAX, using a real browser is key. Using this simulation allows developers to verify the site’s functionality and speed as perceived by a user, but this option has the highest footprint on load injection machines.