On Thu, Sep 29, 2005 at 09:18:28PM +0100, Calum Grant <calum@visula.org> wrote:
Furthermore you could implement a table that can be stored in a file, and used wihout reading all records into memory.
I think the memory-mapped file route would be the most
[mailto:boost-bounces@lists.boost.org] On Behalf Of Andreas Pokorny On Wed, Sep 28, 2005 at 10:50:51PM +0100, Calum Grant <calum@visula.org> wrote: profitable, it
would probably already work.
Interesting, could you give a short overview, how it could already work.
You could use an allocator with RML (or indeed any STL container) that stores the data in a memory-mapped file. This basically makes the data persistent.
That simple? I feared there is more to it. Sounds like RML is written with a lot of care.
I actually had a project a while back that did such a thing, and got some good benchmarks comparing MySQL vs file-mapped containers: http://lightwave.visula.org/persist/bench.html
Looks impressive.
and I'm sure boost::shmem::allocator is similar. Performance is very good. We could devise a benchmark and I'll implement in RML + Persist/Shmem, you implement in SQLlite and we'll see the difference.
Yeah. When do you plan to submit RML to boost? I would really love to see such a library in boost. Regards Andreas