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

[Joe Wilson]

A ^C handler could be created to flush the contents to disk.
As for crashes, c'est la vie. ;-)

Even if this idea is not pursued, getting timings using a ":memory:" 
db would give you a theoretical "ideal" database time. The remaining
time would be mostly attributed to monotone code itself and netsync 
latency.

On another topic, I did not view the Monotone code to see how coarse 
the transactions are. The more database writes grouped together in 
the same transaction, the better the speed. SQLite can run ten times
faster with large transactions instead of single insert/update
operations: http://www.sqlite.org/speed.html

--- Timothy  Brownawell <address@hidden> wrote:
> 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


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com