Web application has frontend and backend and "some features loading more long" may be caused by either slow rendering or slow backend response.
First of all go for your browser developer tools and see where the page spends the most time. At this stage you can also use frontend performance testing tools like Lighthouse
This way you will be able to ...
Given you have jmeter in tags here is a JMeter-related solution.
Load testing is the process ensuring that the application can handle the anticipated load hence the process of load testing a web application is simulating real users using real browsers accessing the web application.
So you don't need to know about the APIs or backend technologies, you need to ...
I think both JMeter and k6 support sending test results to InfluxDB so you can use it as a centralized storage.
JMeter's Backend Listener allows specifying application name, test title, event tags, etc. and all these can be used as filters in i.e. Grafana dashboards
Let's imagine that you have a simple test which runs 10 requests in loop.
9 requests response time is 1 second
10th request takes 10 seconds for any reason
Total test duration would be 20 seconds, average response time will be 1.9 seconds, throughput will be 0.5 requests per second.
In my opinion ignoring or masking this "long" request is a very ...
Your solution with powershell makes sense.
Another idea is to use JMeter Maven Plugin which automatically runs all the scripts it finds under src/test/jmeter folder relative to pom.xml file.
You can also pass parameters via Maven pom.xml file.
More information: How to Use the JMeter Maven Plugin
You cannot extrapolate the results you get for the scaled down environment to the full-size environment, if the scaled down environment has 25% of the production's hardware capacity it doesn't necessarily mean that you will get 4x times better results if you run the same test on production.
You can test:
Code and Database Interaction
External Service Calls
Most probably you need to add HTTP Header Manager and configure it to send Content-Type header with the value of application/json, it might be the case that your API treats the request body as the plain text hence cannot parse the provided data.
Any idea why it's showing an exception ? - it's server-side error, check your application logs for the reason. From JMeter side you can troubleshoot the issue by adding the next line to system.properties file:
and the following lines to log4j2.xml file:
<Logger name="org.apache.http" level="debug" />
It might be the case of not proper configuration of your application server/database/other middleware, for example if the number of concurrent users is higher than the maximum number of connections in the pool - the remaining ones will "wait" until the next connection becomes available for serving them
So double check your application configuration ...