Hi,
If the query takes 19 seconds via the client while connecting
directly to the database and 48 seconds when going through
MaxScale, I'd first measure how much network lag there is and
whether there's a network bandwidth bottleneck somewhere. I'd also
monitor the CPU usage of MaxScale while this query is being
processed by MaxScale.
You should also turn on info level logging by adding log_info=true under the [maxscale] section. This will cause a lot of log message to be logged and the info level logging should not be left on permanently as it'll end up filling the disk up pretty quickly. In the info log messages, you'll see the routing information that MaxScale sends. If you want higher precision timestamps in the log messages, you can add ms_timestamp=true under the [maxscale] section. This will include milliseconds in the log messages.
Markus
--
You received this message because you are subscribed to the Google Groups "MaxScale" group.
To unsubscribe from this group and stop receiving emails from it, send an email to maxscale+u...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/maxscale/33b6506f-87f8-4be6-91ca-8c369d885565n%40googlegroups.com.
-- Markus Mäkelä, Senior Software Engineer MariaDB Corporation