From: Martin Fick <mfick@codeaurora.org>
To: Hilco Wijbenga <hilco.wijbenga@gmail.com>
Cc: Git Users <git@vger.kernel.org>
Subject: Re: Git, Builds, and Filesystem Type
Date: Thu, 9 Feb 2012 16:34:36 -0700 [thread overview]
Message-ID: <201202091634.36563.mfick@codeaurora.org> (raw)
In-Reply-To: <CAE1pOi387-bimYEG4bjFOjaCwhPeDyLRj7wOJgyuKSCrZ9kBFg@mail.gmail.com>
On Thursday, February 09, 2012 04:24:47 pm Hilco Wijbenga
wrote:
> On 9 February 2012 13:53, Martin Fick
<mfick@codeaurora.org> wrote:
> > On Thursday, February 09, 2012 02:23:18 pm Hilco
> > Wijbenga
> >
> > wrote:
> >> For the record, our (Java) project is quite small.
> >> It's 43MB (source and images) and the entire
> >> directory tree after building is about 1.6GB (this
> >> includes all JARs downloaded by Maven). So we're not
> >> talking TBs of data.
> >>
> >> Any thoughts on which FSs to include in my tests? Or
> >> simply which FS might be more appropriate?
> >
> > tmpfs is probably fastest hands down if you can use it
> > (even if you have to back it by swap).
>
> I don't have quite that much RAM. :-)
But I am sure that you have that much disk space which you
can allocate to swap, if not you already couldn't build it.
And tmpfs swapping is still likely faster than a persistent
FS (it will not need to block on syncs). If you are
benchmarking, it is likely worth you effort since that will
probably mark the upper performance bound,
-Martin
--
Employee of Qualcomm Innovation Center, Inc. which is a
member of Code Aurora Forum
next prev parent reply other threads:[~2012-02-09 23:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-09 21:23 Git, Builds, and Filesystem Type Hilco Wijbenga
2012-02-09 21:53 ` Martin Fick
2012-02-09 23:24 ` Hilco Wijbenga
2012-02-09 23:34 ` Martin Fick [this message]
2012-02-10 1:25 ` Hilco Wijbenga
2012-02-10 2:08 ` Martin Fick
2012-02-10 4:04 ` Hilco Wijbenga
[not found] ` <CAE5ih7_NkyJ6vGbyoKvQy65LFK3-zkXi79Xd6+3Si8DyUi47JQ@mail.gmail.com>
2012-02-10 1:11 ` Hilco Wijbenga
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=201202091634.36563.mfick@codeaurora.org \
--to=mfick@codeaurora.org \
--cc=git@vger.kernel.org \
--cc=hilco.wijbenga@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.