|
From: | graydon hoare |
Subject: | [Monotone-devel] Re: Re: using sqlite as provided in debian unstable |
Date: | Wed, 01 Sep 2004 13:25:54 -0400 |
User-agent: | Opera M2/7.53 (Linux, build 737) |
| monotone uses an 8K page size, whereas sqlite 2.8.15 uses a 1K | one. I don't know exactly what implications that difference | has---presumably performance. If I understand things correctly, | this difference will disappear with sqlite 3, but that may not | arrive for a while. Can anyone recall why it was decided necessary to change the page size for sqlite as bundled with monotone? Was it a major improvement in performance, or something else? Can I assume it to be safe to run monotone on a default sqlite page size?
it's a performance thing: small pages overflow too often. it works with either; it just works better with larger pages. anyways, sqlite 3 removes the issue by dynamically resizing pages. the only issue is that sqlite 2 databases made by previous monotones will need to be dumped to text and reloaded if you want to switch page sizes, say if you want to share a database between the debianized monotone and the one I stuck on our homepage. not the end of the world. I think we should be OK with the debian packages. I can put in a faq entry about it if you expect to run into the problem a lot, otherwise I expect the problem to silently vanish when we move to sqlite 3. -graydon
[Prev in Thread] | Current Thread | [Next in Thread] |