Replies: 1 comment 3 replies
-
Hey @jules-ch, just so you're aware, InfluxDB 3.0 open source is still currently under active development and so perf hits like this should be expected while we work on ironing out the kinks/add features. The CLI is using the http endpoint not the GRPC endpoint, but they both go to the same port where we have a service to figure out how to handle the incoming query (e.g. is this an http or a GRPC request). It should be using the same code underneath to run a query. This would be my first guess, but I haven't done any profiling to figure out if that's actually the problem. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm getting different performance between the same SQL request on InfluxDB3 between a CLI call that I believe hit the HTTP v3 POST API and calling with a Flight GRPC Client.
I uploaded a simple 1MB+ of data and calls this simple request.
Performance difference is around 10x between the 2 path that I find odd.
Here are the logs:
CLI call
influxdb3 query --dbname location "SELECT lat as latitude,lon as longitude,battery,time,altitude FROM telemetry ORDER BY time DESC LIMIT 1"
Here E2E duration is
15 ms
With Flight GRPC:
E2E duration goes up to
88 ms
which is almost 6xAnybody got a hint on where this performance hit comes from ?
Beta Was this translation helpful? Give feedback.
All reactions