git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vicent Marti <tanoku@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Jonathan Nieder" <jrnieder@gmail.com>,
	libgit2@librelist.com, git@vger.kernel.org,
	"Nguyễn Thái Ngọc" <pclouds@gmail.com>
Subject: Re: Using libgit2 code in git.git as a Google Summer of Code project?
Date: Fri, 11 Mar 2011 14:22:25 +0200	[thread overview]
Message-ID: <AANLkTinHhHk6U3wTDLUx2f4S17arLWGj4S1NSAw9yM-x@mail.gmail.com> (raw)
In-Reply-To: <7vlj0m4vz1.fsf@alter.siamese.dyndns.org>

Hey,

On Thu, Mar 10, 2011 at 9:27 PM, Junio C Hamano <gitster@pobox.com> wrote:
> How big a performance penalty does libgit2 have to pay to depart from many
> "we run once and let exit take care of cleaning up after us" patterns used
> in git.git primarily in order to avoid the housekeeping cost?

It's not significant. We try to use custom memory allocation wherever
possible, and the most complex structures (interdependencies in parsed
objects from the DAG) are internally garbage collected, so we don't do
any unnecessary free's. We try to offset the cost of 'proper' memory
management by using smarter/more performance tuned algorithms. So far,
some stuff ranges from varying degrees of faster-than-git (see: new
revision walker, index writing, streaming loose object writes) to
slightly slower (see object parsing :/).

We are working on it. Performance is our main concern.

Cheers,
Vicent

      reply	other threads:[~2011-03-11 12:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTinqem5e0+vxzR64s1Y9o7B8RgEFXcm0HV_jeZ4Y@mail.gmail.com>
     [not found] ` <AANLkTikkFDLKn5KMaSTwUABBVX_vYDj8pW1kqmsm1_vy@mail.gmail.com>
2011-03-10 10:13   ` Using libgit2 code in git.git as a Google Summer of Code project? Jonathan Nieder
2011-03-10 10:18     ` Jonathan Nieder
2011-03-10 11:33     ` Vicent Marti
2011-03-10 11:39       ` Nguyen Thai Ngoc Duy
2011-03-10 12:56         ` Vicent Marti
2011-03-13 17:11           ` Ramkumar Ramachandra
2011-03-10 11:55       ` Jonathan Nieder
2011-03-10 19:27         ` Junio C Hamano
2011-03-11 12:22           ` Vicent Marti [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=AANLkTinHhHk6U3wTDLUx2f4S17arLWGj4S1NSAw9yM-x@mail.gmail.com \
    --to=tanoku@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jrnieder@gmail.com \
    --cc=libgit2@librelist.com \
    --cc=pclouds@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 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).