Re: [Monotone-devel] ideas to speed up monotone SQLite database access

[Timothy Brownawell]

On Sun, 2006-02-05 at 14:39 -0800, Joe Wilson wrote:
[...]
> (2) Use a ":memory:" database for the initial monotone pull and then dump the 
> resultant database
> to file. This would eliminate the disk latency entirely. Since most monotone 
> databases I've seen
> are generally under 100 megs, this is a viable option. Naturally, the 
> file-based database must be
> locked during the entire pull/dump operation. Unfortunately, this would 
> prevent more than one user
> from accessing the database at a time.
> 
>  http://www.sqlite.org/cvstrac/wiki?p=InMemoryDatabase

The new netsync code allows a pull to be interrupted without losing
what's already been downloaded. So if an impatient user hits ^C (or the
system crashes, or...) after 10 minutes, the next time they try to pull
they don't have to re-pull the part that they pulled in those 10
minutes. Wouldn't keeping everything in memory kill this feature?

Tim