MySQL’s concurrency control is a limit on the total number of threads that can be active at once, across all queries.
Traffic Control limits concurrency and resource use according to configurable metadata like the username, remote address, or the contents of any sqlcommenter tags included in the query. So you can say things like “the batch processing role can’t run more than four queries at a time.” The finer granularity is key.
We’ve got a separate blog post all about how traffic control works: https://planetscale.com/blog/behind-the-scenes-how-traffic-c...
It sounds vaguely like InnoDB’s concurrency control solution which uses tokens [0] as a unit of maximum work a query can perform.
0: https://dev.mysql.com/doc/refman/8.4/en/innodb-performance-t...
MySQL’s concurrency control is a limit on the total number of threads that can be active at once, across all queries.
Traffic Control limits concurrency and resource use according to configurable metadata like the username, remote address, or the contents of any sqlcommenter tags included in the query. So you can say things like “the batch processing role can’t run more than four queries at a time.” The finer granularity is key.
tickets, not tokens, but yeah