Using cassandra 4.0, I activated tracing for statements (not for all of them), I also measure the time for session.execute (call it client side duration) and compare it to the trace value from getDurationMicros (call it server side duration)
sample 1:
- Server side duration: 1750ms
- Client side duration: 3250ms
sample 2:
- Server side duration: 65ms
- Client side duration: 3200ms
Notes:
- Network should not be a real overhead Client is hosted in spring boot
- application running tomcat.
- No more than 15 in-flight requests measured
Questions:
what clould be the reasons for this client side overhead? what kind of client side tuning is relevant or should be checked\modified?