Preetam
Preetam
Pure was added in https://github.com/Preetam/explain-analyzer/commit/d7278119adf7f9469e890ba5f5a28ecdc507cd6b. Should've made a PR for that 🤦♂️ .
https://preetam.github.io/explain-analyzer/#!/explain/3b0bb4c994eb6e79dccafb58682fe90860e41938.json * Comments are repetitive. Just mention FTS once and list the tables affected.
Most important thing to highlight: FTS with lots of rows examined per scan.
A typical time series workload (at least in my experience) has lots of frequent random writes and occasional large scan reads. The records would be like (series ID, timestamp) =>...
Oh, and it would be great to see how throughput and latency changes with various numbers of concurrent readers and writers.
I believe 5.7.11 right now.
Yes, MySQL Community. We're not using Percona Server.
Also group by flooring a timestamp.
Let's leave this until the redesign. **Blocked.**
The `Seek` function doesn't make sense if you can't notify the storage resource about ordering...