From: Martin Langhoff <martin.langhoff@gmail.com>
To: Sascha Silbe <sascha-ml-reply-to-2009-2@silbe.org>, git@vger.kernel.org
Subject: Re: crash proof / recovery from power loss
Date: Thu, 25 Jun 2009 15:31:29 +0200 [thread overview]
Message-ID: <46a038f90906250631k5e702f66g50a6e60db8bab856@mail.gmail.com> (raw)
In-Reply-To: <20090623210556.GB31015@twin.sascha.silbe.org>
On Tue, Jun 23, 2009 at 11:05 PM, Sascha Silbe
<sascha-ml-devel-vcs-git@silbe.org> wrote:
> I'm going to use git as a back end for the Sugar data store / Journal. [1]
> One thing I'm worried about is how it's going to behave if a crash (e.g. power loss - no corruption) occurs.
> What can happen in such a case? Is it always recoverable and if so, how?
Git is outrageously good in keeping things sane. On that front, you
won't see any problems.
Now... there is one area where it will hurt lots: storing large binary
blobs. Git assumes that every file is very small in comparison with
available physical memory.
- Sugar utilities already can create files larger than available
memory. Think Record.xo, etoys, etc.
- Many sugar target platforms are _very_ memory constrained. XO-1
being the prime example.
Lots of what git does would be good in the Journal. But some of the
core assumptions are not well matched.
There are some tunables in git that might help. And maybe you can
sidestep the harder corners of the problem by having a threshold, and
handling large files separately.
hth,
m
--
martin.langhoff@gmail.com
martin@laptop.org -- School Server Architect
- ask interesting questions
- don't get distracted with shiny stuff - working code first
- http://wiki.laptop.org/go/User:Martinlanghoff
prev parent reply other threads:[~2009-06-25 13:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-23 21:05 crash proof / recovery from power loss Sascha Silbe
2009-06-25 13:11 ` Jakub Narebski
2009-06-25 13:31 ` Martin Langhoff [this message]
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=46a038f90906250631k5e702f66g50a6e60db8bab856@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=git@vger.kernel.org \
--cc=sascha-ml-reply-to-2009-2@silbe.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).