From: "Martin Langhoff (CatalystIT)" <martin@catalyst.net.nz>
To: Shawn Pearce <spearce@spearce.org>
Cc: martyn@catalyst.net.nz, Junio C Hamano <junkio@cox.net>,
git@vger.kernel.org
Subject: Re: [PATCH] Use column indexes in git-cvsserver where necessary.
Date: Mon, 23 Oct 2006 19:02:01 +1300 [thread overview]
Message-ID: <453C5AD9.4030008@catalyst.net.nz> (raw)
In-Reply-To: <20061023050934.GA25018@spearce.org>
Shawn Pearce wrote:
> Tonight I found a git-cvsserver instance spending a lot of time in
> disk IO while trying to process operations against a Git repository
> with >30,000 objects contained in it.
>
> Blowing away my SQLLite database and rebuilding all tables with
> indexes on the attributes that git-cvsserver frequently runs queries
> against seems to have resolved the issue quite nicely.
>
> Since the indexes shouldn't hurt performance on small repositories
> and always helps on larger repositories we should just always create
> them when creating the revision storage tables.
>
> Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Ack.
I am thinking we need a lightweight schema versioning mechanism to
decide whether the DB schema needs changes such as this. Too much work
for this though. ;-)
We have a simple one in Moodle I could port when the time comes.
cheers,
martin
--
-----------------------------------------------------------------------
Martin @ Catalyst .Net .NZ Ltd, PO Box 11-053, Manners St, Wellington
WEB: http://catalyst.net.nz/ PHYS: Level 2, 150-154 Willis St
OFFICE: +64(4)916-7224 MOB: +64(21)364-017
Make things as simple as possible, but no simpler - Einstein
-----------------------------------------------------------------------
prev parent reply other threads:[~2006-10-23 6:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-23 5:09 [PATCH] Use column indexes in git-cvsserver where necessary Shawn Pearce
2006-10-23 6:02 ` Martin Langhoff (CatalystIT) [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=453C5AD9.4030008@catalyst.net.nz \
--to=martin@catalyst.net.nz \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=martyn@catalyst.net.nz \
--cc=spearce@spearce.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).