From: Pieter Wuille <pieter.wuille@gmail•com>
To: Mike Hearn <mike@plan99•net>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] LevelDB benchmarking
Date: Tue, 19 Jun 2012 13:38:59 +0200 [thread overview]
Message-ID: <20120619113857.GA29542@vps7135.xlshosting.net> (raw)
In-Reply-To: <CANEZrP2q9a_0rFh+oo6iUFF1goWs0OJO1xPvxC9zqNA-6VnFAQ@mail.gmail.com>
On Tue, Jun 19, 2012 at 11:05:20AM +0200, Mike Hearn wrote:
> OK, to make progress on this work I need a few decisions (Gavin?)
>
> 1) Shall we do it?
I'm all for moving away from BDB. It's a very good system for what it is
intended for, but that is not how we use it. The fact that it is tied to
a database environment (but people want to copy the files themselves
between systems), that is provides consistency in case of failures (but
because we remove old log files, we still see very frequent corrupted
systems), the fact that its environments are sometimes not even forward-
compatible, ...
Assuming LevelDB is an improvement in these areas as well as resulting in
a speed improvement, I like it.
> 2) LevelDB is obscure, new and has a very minimalist build system. It
> supports "make" but not "make install", for example, and is unlikely
> to be packaged. It's also not very large. I suggest we just check the
> source into the main Bitcoin tree and link it statically rather than
> complicate the build.
How portable is LevelDB? How well tested is it? What compatibility
guarantees exist between versions of the system?
I don't mind including the source code; it doesn't seem particularly
large, and the 2-clause BSD license shouldn't be a problem.
> 3) As the DB format would change and a slow migration period
> necessary, any other tweaks to db format we could make at the same
> time? Right now the key/values are the same as before, though using
> satoshi serialization for everything is a bit odd.
>
> We'd need UI for migration as well.
Jeff was working on splitting the database into several files earlier, and
I'm working on the database/validation logic as well. Each of these will
require a rebuild of the databases anyway. If possible, we should try to
get them in a single release, so people only need to rebuild once.
PS: can we see the code?
--
Pieter
next prev parent reply other threads:[~2012-06-19 11:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 18:41 Mike Hearn
[not found] ` <CAAS2fgTNqUeYy+oEFyQWrfs4Xyb=3NXutvCmLusknF-18JmFQg@mail.gmail.com>
2012-06-19 9:05 ` Mike Hearn
2012-06-19 11:38 ` Pieter Wuille [this message]
2012-06-19 15:05 ` Gavin Andresen
2012-06-19 16:06 ` Mike Hearn
2012-06-19 19:22 ` Stefan Thomas
2012-06-20 9:44 ` Mike Hearn
2012-06-20 9:53 ` Mike Hearn
2012-06-20 11:37 ` Pieter Wuille
2012-06-20 12:41 ` Mike Hearn
2012-06-25 16:32 ` Mike Hearn
2012-07-21 18:49 ` Mike Hearn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120619113857.GA29542@vps7135.xlshosting.net \
--to=pieter.wuille@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=mike@plan99$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox