5 ms·

Kudos to the team; some great releases this summer! (10x insert performance, regex queries, and now date/time and better disk space--all in ~90 days!) I had ne

Kudos to the team; some great releases this summer! (10x insert performance, regex queries, and now date/time and better disk space--all in ~90 days!) I had never looked in to how rdb used disk space and off the cuff attributed its high usage to something similar to Mongo and allocating blocks ahead of usage. This was something that went in to the negative column for me when I evaluated using rdb vs Postgres for a JSON dump. 12k somewhat light (but still larger than 250b) records ate up over 70MB of disk space in just over a couple days and I've not looked back. Time to give it another spin!

coffeemug 13y ago
There is no technical reason why Rethink needs to have high disk usage. We got much better with this release, and will continue to get even better in the long term. (Squeezing more optimizations does get a bit harder, though)
- continuations 13y ago
  How does rethinkDB's disk usage compare to MySQL and Psotgres?
yogo 13y ago
This is good to hear and will make me try it too. High disk space utilization was something I experienced with mongodb back in the day and that caused me to lose interest (not sure if they're better about it these days). There's probably a trade-off between speed and having blocks allocated but it starts becoming a problem on smaller vps environments.
- werkshy 13y ago
  Mongo got a lot better about reusing disk space in v2.2, if you are deleting from a collection. Still no compression or document field name optimizations though.
  - leif 13y ago
    Couldn't resist: try tokumx if you want "mongodb with compression". There isn't a speed/space usage tradeoff. Our latest blog post is about long field names: http://www.tokutek.com/2013/08/tokumx-tip-create-any-field-name-you-want/ http://www.tokutek.com/2013/08/tokumx-tip-create-any-field-n...
    - yogo 13y ago
      Interesting product. They also have a mariadb engine (different use cases).

coffeemug 13y ago

There is no technical reason why Rethink needs to have high disk usage. We got much better with this release, and will continue to get even better in the long term. (Squeezing more optimizations does get a bit harder, though)

continuations 13y ago
How does rethinkDB's disk usage compare to MySQL and Psotgres?

yogo 13y ago

This is good to hear and will make me try it too. High disk space utilization was something I experienced with mongodb back in the day and that caused me to lose interest (not sure if they're better about it these days). There's probably a trade-off between speed and having blocks allocated but it starts becoming a problem on smaller vps environments.

werkshy 13y ago
Mongo got a lot better about reusing disk space in v2.2, if you are deleting from a collection. Still no compression or document field name optimizations though.
- leif 13y ago
  Couldn't resist: try tokumx if you want "mongodb with compression". There isn't a speed/space usage tradeoff. Our latest blog post is about long field names: http://www.tokutek.com/2013/08/tokumx-tip-create-any-field-name-you-want/ http://www.tokutek.com/2013/08/tokumx-tip-create-any-field-n...
  - yogo 13y ago
    Interesting product. They also have a mariadb engine (different use cases).