[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Monotone-devel] file-system archaeology
From: |
Zack Weinberg |
Subject: |
Re: [Monotone-devel] file-system archaeology |
Date: |
Tue, 28 Apr 2009 15:18:06 -0700 |
On Tue, Apr 28, 2009 at 3:04 PM, Zack Weinberg <address@hidden> wrote:
> On Tue, Apr 28, 2009 at 2:15 PM, <address@hidden> wrote:
>>
>> I wonder what all that overhead is doing.
>
> What does 'mtn db info' print for these databases?
I poked at this a little. SQLite database files are divided into
pages; we set each page to be 8192 bytes long. There is one page of
metadata (there could be more if we had a more complicated database
schema), and each table or index occupies at least one page, even when
empty. Our schema consists of 15 tables and 22 indexes. So, a
totally empty database is 1 + 15 + 22 = 38 pages, and if you multiply
that by 8192 you get 311296 bytes.
Your old database was probably created at a time when we set a smaller
page size; the page size cannot be changed after any tables are
created. 'mtn db info' will say.
zw