Show HN: SummitDB – In-Memory NoSQL DB

Re:Show HN: SummitDB – In-Memory NoSQL DB by qwertyuiop924 on Wednesday October 12, 2016 @06:16AM (#12691634)

Thanks for the suggestions. Some of those might work. The only problem with k/v stores is the serialization/deserialization cost, as most of them can only store strings.

[ Parent | on HN ]

Re:Show HN: SummitDB – In-Memory NoSQL DB by erichocean on Wednesday October 12, 2016 @04:30PM (#12696204)

> The only problem with k/v stores is the serialization/deserialization cost, as most of them can only store strings.

I store Cap'n Proto objects directly into LMDB, and can read them without any memory allocation or deserialization cost. Freaking rocks.

[ Parent | on HN ]

Re:Show HN: SummitDB – In-Memory NoSQL DB by ddorian43 on Wednesday October 12, 2016 @06:47AM (#12691775)

lmdb has some special cases where you can store capnproto/flat-buffers objects and read without copying/deserializing!

[ Parent | on HN ]

Re:Show HN: SummitDB – In-Memory NoSQL DB by qwertyuiop924 on Wednesday October 12, 2016 @07:39AM (#12691969)

Really? that could be useful...

[ Parent | on HN ]

Re:Show HN: SummitDB – In-Memory NoSQL DB by ddorian43 on Wednesday October 12, 2016 @08:01AM (#12692059)

LMDB can hand you back a pointer to your object in the memory map, and we can easily use that pointer with Cap'n Proto without any calls to malloc(). source: https://news.ycombinator.com/item?id=12394385

[ Parent | on HN ]