Optimizing Web Applications
Last updated
Was this helpful?
Last updated
Was this helpful?
This page intends to provide some guidance in optimizing web applications. Please refer to the for the list of component types, parameters, metrics, and constraints.
No specialized telemetry solution to gather Web Application metrics is included. The following providers however can integrate with the provided metrics:
: this provider can be configured to ingest data points generated by any monitoring application able to export the data in CSV format.
integrations leveraging , or as a load generator can use this ad-hoc provider that comes out of the box and uses the metrics defined in this optimization pack.
The provided component type does not define any parameter. The workflow will optimize parameters defined in other component types representing the underlying technological stack.
A typical workflow to optimize a web application is structured in three parts:
Configure and restart the application
Use the to interpolate the tuned parameters in the configuration files of the underlying stack.
Restart the application using an .
Wait for the application to come up using the or .
Run the test
use any of the to trigger the execution of the performance test against the application.
Perform the cleanup
use any of the to restore the application to the original state.
Here's an example workflow to perform a test on a Java web application using NeoLoad as a load generator:
See this for an example of a study leveraging the Web Application pack.