git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH] git-p4: improve performance with large files

From
Sam Hocevar <sam@zoy.org>
Date
Mar 4, 2009, 21:54 UTC
Message-ID
<20090304215438.GA12653@zoy.org>
   The current git-p4 way of concatenating strings performs in O(n^2)
and is therefore terribly slow with large files because of unnecessary
memory copies. The following patch makes the operation O(n).
   Using this patch, importing a 17GB repository with large files
(50 to 500MB) takes 2 hours instead of a week.
Signed-off-by: Sam Hocevar <sam@zoy.org>
---
 contrib/fast-import/git-p4 |    5 +++--
 1 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/contrib/fast-import/git-p4 b/contrib/fast-import/git-p4
index 9fdb0c6..09e9746 100755
--- a/contrib/fast-import/git-p4
+++ b/contrib/fast-import/git-p4
@@ -990,11 +990,12 @@ class P4Sync(Command):
         while j < len(filedata):
             stat = filedata[j]
             j += 1
-            text = ''
+            data = []
             while j < len(filedata) and filedata[j]['code'] in ('text', 'unicode', 'binary'):
-                text += filedata[j]['data']
+                data.append(filedata[j]['data'])
                 del filedata[j]['data']
                 j += 1
+            text = "".join(data)
 
             if not stat.has_key('depotFile'):
                 sys.stderr.write("p4 print fails with: %s\n" % repr(stat))
-- 
1.6.1.3
Next: thestar@fussycoder.id.au
Message 1 of 10 in “git-p4: improve performance with large files”
  1. git-p4: improve performance with large filesSam Hocevar, Mar 4, 2009
  2. thestar@fussycoder.id.auMar 4, 2009
  3. Sam HocevarMar 5, 2009
  4. thestar@fussycoder.id.auMar 6, 2009
  5. Junio C HamanoMar 6, 2009
  6. Han-Wen NienhuysMar 6, 2009
  7. Sam HocevarMar 6, 2009
  8. Junio C HamanoMar 6, 2009
  9. git-p4: improve performance with large filesSam Hocevar, Mar 6, 2009
  10. git-p4: improve performance when importing huge files by reducing the number of string concatenations while constraining memory usage.Sam Hocevar, Mar 7, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.