Query Timeouts That Follow the Query, Not the User
ProxySQL 3.0.10 lets a hostgroup carry its own default_query_timeout, so the analytics replicas and the OLTP writers can have different limits without writing a single query rule.
ProxySQL 3.0.10 lets a hostgroup carry its own default_query_timeout, so the analytics replicas and the OLTP writers can have different limits without writing a single query rule.
ProxySQL's new routing algorithm to handle hundreds of thousands of schemas/shards ProxySQL is a service designed to scale and handle traffic in very large setups. In the past we already showed examples of how ProxySQL can handle thousands of MySQL servers, and millions (yes, millions!) of distinct...
In a previous post I wrote about how read/write split is implemented in ProxySQL, and what I believe is the best practice for read/write split on top of MySQL servers: start sending all traffic to MySQL master identify what queries can be routed to the MySQL
Query routing is one of the core features of ProxySQL. Read/write split is perhaps one of the most common query routing use, while the other most commonly used
One of ProxySQL most interesting features is query rewrite. This functionality is one of the main reasons to write a proxy that sits between the applicatio