Ticket queue
The 50 most recent open tickets (real demo data, read-only). Tap a ticket to read it and its comments.
- Loading…
Open a demo ticket
Choose a subject and a priority. There is no free text.
Three steps: the write goes to the primary. A plain read right after it goes to a replica, which may not have the row yet. The same read inside a transaction stays on the primary and always finds it.
Where did my query go?
Your last 20 requests, newest first: the instance, its role and the time the database took.
- No requests yet.
Live soak
The always-on TicketDesk workload, last 5 minutes. Refreshed every 5 seconds.
| Loading… |
Visitor reads by instance
Plain reads made by all visitors of this page, last 10 minutes.
| No visitor reads yet. |
Read this before you draw conclusions
- Stale reads are normal. Replication to the replicas is asynchronous. A plain read right after a write can miss the new row. Splitting reads from writes trades read-your-writes for scale; a transaction keeps your reads on the primary.
- The primary can also answer plain reads. The reader group includes the writer (ProxySQL's writer-is-also-reader setting, on by default in ProxySQL SaaS). Such a read says “writer”.
- Cached answers repeat an old instance. When a presenter turns on ProxySQL's query cache for a query, its cached answers name the instance that first answered. The queries on this page are written so that the demo's cache rule never matches them.
- This page changes nothing in ProxySQL. It has no admin function. A presenter changes routing in the ProxySQL SaaS console, and you see the effect here.