I am testing a API endpoint via postman
Postman screenshot
The transfer start time period is 1271.98ms which is a bit longer than I expected.
I check the Cloudwatch logs for this request, the integration latency for it is62ms.
API-Gateway log
Because this transfer start time period displayed by postman doesn't contain DNS lookup, TCP/SSL handshake. I am curious why there is such a difference due to the endpoint processing is quite fast.
I expect postman transfer start time period is the same as API-Gateway integration latency.
Related
I have an Rest API hosted in Azure function, exposed via Azure APIM. The total execution time of the API is 1 to 2 seconds via postman. Below is the time split up in Postman. The DNS look up is 400ms and SSL handshake is 1154 ms. Could this be reduced.
I'm getting an error of "gateway timeout. The gateway did not receive a timely response from the upstream server or application." What I'm doing is I'm getting data from sticky CRM by API and storing it into my database and it takes much time to execute. What I noticed is that I'm getting this error right after one minute. So I want to increase that time. I have install web server under ec2 instance and database under rds. I want to increase my gateway time from one minute to infinite or 15-20 minutes.
Help will be appreciated.
Thanks.
I have AWS Elastic load balancer which has two healthy instances. If I make a POST request, it gets accepted. But consequent requests throw 504 gateway timeout error. After 5-10 minutes, it accepts 2-4 requests, and then start throwing 504 error. I try to reach is Spring Boot Application hosted on these two instances. There are no application level timeouts. Further time duration between failed and accepted requests vary, so I believe no fixed timeout configuration setting is causing an issue. How can I resolve this?
Scenario:
A JMeter script for a single user with a single HTTP request is configured to run via localhost port 8888 (port sniffed by Fiddler).
The request travels properly to the server and a successful response is received.
The issue is, the Average time displayed in the Listener for the HTTP response in not matching with the overal elapsed time of Fiddler for that request.
e.g. If the Average time displayed is of 24 millisecond, Fiddler reports 15 millisecond (Note: high-resolution timers enabled in Fiddler)
I am trying to figure out why is JMeter consuming a small bit of extra time for each request, what network or system processing element its considering additional to those of Fiddler.
JMeter consumes a bit of extra time when you run in GUI mode. In Non- GUI the response is better. The details on response time can be read here JMeter - response time calculation
I have a Vaadin application that is using web sockets (Atmosphere) to push data to the browser. This means that there is no normal HTTP request/response cycle. From the looks of it, I do get HTTP GET requests, but the response is pushed out via the web socket asynchronously.
Because of this the response time (and message size) metrics I can get from the web server logs are useless.
How can I get information logged as to how long every request processing took?
Chrome Developer Tools allows you to see time stamps of messages sent using web sockets (in the Network tab).