> We are getting ready to start using in- > memory database to cache sqlite reads/writes > in effort to improve speed. For background, > the application is an email client. > > The way we envision the caching working is > that we have a mirror copy of any table in > use in memory. The tables are small and not > many are in use at any time, so we are ok with > space. Since we read much more than we > write, reading from memory should improve. > Also, this should simplify our transaction > model for transacted objects. > > Has anyone done this? Comments?
It sounds like overkill to me too. In memory databases are unique per connection. If you have multiple processes they won't be able to share the same database. You could share the same database amoung threads or a database server process. Using the 90/10 rule this last 10% of performance is going to cost you 90% of the effort.
