- I'm in tbruce0's Mixlr, which isn't as odd as it sounds. https://t.co/FybIwh2d3n #mixlr 20:08:15, 2016-10-31
- RT @sglassmeyer: I wonder if instead of/in addition to hackathons – which I'm not sold on value of – someone could host lawyer code boot ca… 20:12:40, 2016-10-31
- RT @carlmalamud: The fraudulent aspect of PACER charges is algorithm for html pages, badly broken. Can easily rack up huge bills on searche… 21:19:25, 2016-10-31
The MySQL n00b: MyRocks: migrating a large MySQL dataset from InnoDB to RocksDB to reduce footprint
Enter RocksDB and the LSM (Log Structured Merge) technology: we are entering a new planet as far as data storage goes. The idea of an “append only” type of approach for writing database rows is something I never heard before. Databases usually are the most random writer ever! And although SSD will not suffer from write randomness, there are other factors that need to be taken into consideration. I’ll not go into more details about how LSM or RocksDB work, or why LSM is good for your SSD and your workload, as there is plenty of information about it on Mark’s blog (see above) or on the official page for RocksDB and for MyRocks (the RocksDB engine for MySQL) on GitHub; just check the Wiki there.
Source: The MySQL n00b: MyRocks: migrating a large MySQL dataset from InnoDB to RocksDB to reduce footprint
MyRocks and RocksDB sound like something worth exploring even for our small big data tables.