Tracing Lettuce, Command Duration - What does it really measure?

[SimoneGiusso]

I didn't find any reference explaining exactly what the duration specified in the trace, really indicates. I'm trying to analyze some slow http requests, and I see some MGET redis requests taking even 750 ms to run. But what this duration includes? This is what I suppose it includes:

• Network Latency: Time for the request to travel from the client to the server and back.

• Server Processing Time: Time taken by the server to process the request (in this case, the /assets/discover endpoint).

• Database or Cache Access Time: If the operation involves querying a database or a cache (e.g., Redis), the time spent on these operations is also included.

• Application Logic: Any time taken by the application in handling the request, like reading from the socket and deserialize the response.

I'm not sure about the last one. But what I like to know is, if I can exclude at least latencies coming from the app. So I can be sure the app is not the problem. Otherwise the trace is not helping much. Too many variables to consider.