Recommend a fast & scalable persistent Map - Java

Recommend a fast & scalable persistent Map - Java

I need a disk backed Map structure to use in a Java app. It must have the following criteria:

1. Capable of storing millions of records (even billions)
2. Fast lookup - the majority of operations on the Map will simply to see if a key already exists. This, and 1 above are the most important criteria. There should be an effective in memory caching mechanism for frequently used keys.
3. Persistent, but does not need to be transactional, can live with some failure. i.e. happy to synch with disk periodically, and does not need to be transactional.
4. Capable of storing simple primitive types - but I don't need to store serialised objects.
5. It does not need to be distributed, i.e. will run all on one machine.
6. Simple to set up & free to use.
7. No relational queries required

Records keys will be strings or longs. As described above reads will be much more frequent than writes, and the majority of reads will simply be to check if a key exists (i.e. will not need to read the keys associated data). Each record will be updated once only and records are not deleted.

I currently use Bdb JE but am seeking other options.

---

Update

Have since improved query performance on my existing BDB setup by reducing the dependency on secondary keys. Some queries required a join on two secondary keys and by combining them into a composite key I removed a level of indirection in the lookup which speeds things up nicely.

Answer by mlk for Recommend a fast & scalable persistent Map - Java

I'd likely use a local database. Like say Bdb JE or HSQLDB. May I ask what is wrong with this approach? You must have some reason to be looking for alternatives.

In response to comments: As the problem performance and I guess you are already using JDBC to handle this it might be worth trying HSQLB and reading the chapter on Memory and Disk Use.

Answer by Boris Pavlovi for Recommend a fast & scalable persistent Map - Java

I think Hibernate Shards may easily fulfill all your requirements.

Answer by David Crawshaw for Recommend a fast & scalable persistent Map - Java

SQLite does this. I wrote a wrapper for using it from Java: http://zentus.com/sqlitejdbc

As I mentioned in a comment, I have successfully used SQLite with gigabytes of data and tables of hundreds of millions of rows. If you think out the indexing properly, it's very fast.

The only pain is the JDBC interface. Compared to a simple HashMap, it is clunky. I often end up writing a JDBC-wrapper for the specific project, which can add up to a lot of boilerplate code.

Answer by james for Recommend a fast & scalable persistent Map - Java

JBoss (tree) Cache is a great option. You can use it standalone from JBoss. Very robust, performant, and flexible.

Answer by Juha Syrjl for Recommend a fast & scalable persistent Map - Java

You may want to look into OrientDB.

Answer by Joel for Recommend a fast & scalable persistent Map - Java

I've found Tokyo Cabinet to be a simple persistent Hash/Map, and fast to set-up and use.

This abbreviated example, taken from the docs, shows how simple it is to save and retrieve data from a persistent map:

    // create the object      HDB hdb = new HDB();      // open the database      hdb.open("casket.tch", HDB.OWRITER | HDB.OCREAT);      // add item       hdb.put("foo", "hop");      hdb.close();  

Answer by Andrejs for Recommend a fast & scalable persistent Map - Java

JDBM3 does exactly what you are looking for. It is a library of disk backed maps with really simple API and high performance.

UPDATE

This project has now evolved into MapDB http://www.mapdb.org

Answer by Harvinder Singh for Recommend a fast & scalable persistent Map - Java

You can try Java Chronicles from http://openhft.net/products/chronicle-map/ Chronicle Map is a high performance, off-heap, key-value, in memory, persisted data store. It works like a standard java map

Fatal error: Call to a member function getElementsByTagName() on a non-object in D:\XAMPP INSTALLASTION\xampp\htdocs\endunpratama9i\www-stackoverflow-info-proses.php on line 72