4 ms·
I work with Baron, the author. He gave a talk recently at SCaLE[0] about our time series storage using MySQL. The slides[1] are also available in case you don't
by misframer 12y ago
I work with Baron, the author. He gave a talk recently at SCaLE[0] about our time series storage using MySQL. The slides[1] are also available in case you don't want to watch the entire talk.
[0] http://youtu.be/EoUfkkrIbPg http://youtu.be/EoUfkkrIbPg
[1] http://www.slideshare.net/vividcortex/scaling-vividortexs-big-data-systems-on-mysql http://www.slideshare.net/vividcortex/scaling-vividortexs-bi...
- Rapzid 12y agoThanks very much. I have experimented with used Riak as a backend with its search 2.0(lucene) for indexing the streams. I'm very interested in how the MySQL tables are laid out; On the watch/reading list for tonight :)
- Rapzid 12y agoI'm wondering if it has been considered to buffer the metrics into a memory table so they can participate in queries, and then let MySQL flush them to durable tables at regular intervals?
- misframer 12y agoMy personal opinion on that is that it's another layer of complexity without too much to gain. It's something else to manage (operational overhead), and something else to interact with (programmer overhead). MySQL by itself is plenty fast for us. As Baron mentioned, we don't even run the database servers at full capacity.