Is there any mechanism (in ODB 2.2.x) to "pin" a specific table in a database in memory?
Essentially, within a normal plocal disk-backed database, I want to select a specific table that is always guaranteed to be in memory (obviously my application is making sure that this table is maintained in such a way that it doesn't grow later than the available memory, while still allowing plenty of memory for general caching, etc.). I still want the "in memory" table to be persisted to disk, but want it to be "pinned" to ensure the highest level of performance on reads. (Note that I don't expect that the "first read" of a particular record after a server restart would already be in memory, although that would be nice future enhancement--active pre-loading from disk of a designated "pinned" table). I could almost accomplish what I'm looking for by creating a small in-memory database with just this one table, but in addition to this table not being persisted to disk, it also makes it more difficult to interact with other tables in the "main" database when necessary. And the other downside is that in-memory databases can't currently be replicated (planned for 3.0: http://orientdb.com/docs/last/Roadmap.html). Just out of curiosity, is this still on track? --Eric -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
