3 ms·
The MapDB mentioned in this article looks pretty interesting: https://github.com/jankotek/MapDB https://github.com/jankotek/MapDB. Anyone have experience with i
by _delirium 14y ago
The MapDB mentioned in this article looks pretty interesting: https://github.com/jankotek/MapDB https://github.com/jankotek/MapDB. Anyone have experience with it?
- spartango 14y agoI've been using the previous version of the library (JDBM3) for some time now, although I haven't tried MapDB just yet. They have very similar APIs, however. I've found JDBM3 a pleasure to use; it's fast and stable, with an excellent API. It's really quite easy to start using (it exposes Java collection interfaces), but you can configure it to do some powerful things under the hood. I'm not using the library in a really high-performance setting (just need a persistent key-value store), so I can't quite comment on the extreme scaling qualities. I'm excited to switch to MapDB as it matures.
- hncommenter13 14y agoI've used JDBM3 to build a high-speed geocoder from US Census Tiger data. Because the data set is static and read-only, I use a minimal perfect hash function to map zip|street pairs to ids and then JDBM to map those ids to compressed strings of data. I have < 25M entries in JDBM, so not an envelope-pushing use case. I'm on an old XP machine with very little memory and a slow disk, and I get quite good performance out of it, despite not being able to effectively use mapped or off-heap memory. I expect that moving to MapDB on JDK7 (with its concurrent collections and better memory allocation) will improve performance quite a bit.