git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Thomas Rast <trast@student.ethz.ch>
To: Jeff King <peff@peff.net>
Cc: <git@vger.kernel.org>
Subject: [git wiki PATCH 1/3] "Improving parallelism in various commands" project
Date: Fri, 2 Mar 2012 12:05:45 +0100	[thread overview]
Message-ID: <57e8b4eb7a98af33982c2f3a763e18f62b1d6d6d.1330686331.git.trast@student.ethz.ch> (raw)
In-Reply-To: <20120302091114.GA3984@sigill.intra.peff.net>

---
 SoC-2012-Ideas.md |   31 +++++++++++++++++++++++++++++++
 1 file changed, 31 insertions(+)

diff --git a/SoC-2012-Ideas.md b/SoC-2012-Ideas.md
index 29a374a..145b379 100644
--- a/SoC-2012-Ideas.md
+++ b/SoC-2012-Ideas.md
@@ -68,3 +68,34 @@ work to be done:
    and only accessed on demand.
 
 Proposed mentor: Jeff King
+
+Improving parallelism in various commands
+-----------------------------------------
+
+Git is mostly written single-threaded, with a few commands having
+bolted-on extensions to support parallel operation (notably git-grep,
+git-pack-objects and the core.preloadIndex feature).
+
+We have recently looked into some of these areas and made a few
+optimizations, but a big roadblock is that pack access is entirely
+single-threaded.  The project would consist of the following steps:
+
+ * In preparation (the half-step): identify commands that could
+   benefit from parallelism.  `git grep --cached` and `git grep
+   COMMIT` come to mind, but most likely also `git diff` and `git log
+   -p`.  You can probably find more.
+
+ * Rework the pack access mechanisms to allow the maximum possible
+   parallel access.
+
+ * Rework the commands found in the first step to use parallel pack
+   access if possible.  Along the way, document the improvements with
+   performance tests.
+
+The actual programming must be done in C using pthreads for obvious
+reasons.  At the very least you should not be scared of low-level
+programming.  Prior experience and access to one or more multi-core
+computers is a plus.
+
+Proposed by: Thomas Rast
+Possible mentor(s): Thomas Rast
-- 
1.7.9.2.467.g7fee4

  reply	other threads:[~2012-03-02 11:05 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-02  9:11 GSoC 2012 application process Jeff King
2012-03-02 11:05 ` Thomas Rast [this message]
2012-03-02 11:05   ` [git wiki PATCH 2/3] "Designing a faster index format" project Thomas Rast
2012-03-02 11:08     ` Jeff King
2012-03-02 18:24     ` Junio C Hamano
2012-03-03  3:30       ` Nguyen Thai Ngoc Duy
2012-03-02 11:05   ` [git wiki PATCH 3/3] "Improving the `git add -p` interface" project Thomas Rast
2012-03-02 14:29   ` [git wiki PATCH 1/3] "Improving parallelism in various commands" project Nguyen Thai Ngoc Duy
2012-03-02 17:35   ` James Pickens
2012-03-02 14:52 ` GSoC 2012 application process Nguyen Thai Ngoc Duy
2012-03-02 21:48 ` Junio C Hamano
2012-03-03  0:09   ` Jeff King
2012-03-03 21:14 ` [git wiki PATCH] "Modernizing and expanding Git.pm" project Jakub Narebski
2012-03-03 22:23   ` Jeff King
2012-03-04 23:35 ` [git wiki PATCH] Teaching "--3way" to "git apply" Junio C Hamano
2012-03-05  5:33   ` Jeff King
2012-03-05  8:05     ` Thomas Rast
2012-03-05 10:02       ` Jeff King
2012-03-05 13:38 ` GSoC 2012 application process Matthieu Moy
2012-03-05 13:58   ` Jeff King
2012-03-05 14:42     ` Matthieu Moy
2012-03-05 23:53       ` Jeff King
2012-03-07 14:36 ` GSoC backup admin Jeff King
2012-03-07 15:27   ` Shawn Pearce
2012-03-08 21:18 ` [gsoc2012 wiki PATCH] "Use JavaScript library / framework in gitweb" project Jakub Narebski
2012-03-09  7:24   ` Jeff King
2012-03-10  0:46 ` [gsoc2012 wiki PATCH] "`git instaweb --serve`" project Jakub Narebski
2012-03-11 22:30 ` [gsoc2012 wiki PATCH] "Graphical diff in git-gui" project Jakub Narebski

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=57e8b4eb7a98af33982c2f3a763e18f62b1d6d6d.1330686331.git.trast@student.ethz.ch \
    --to=trast@student.ethz.ch \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).