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

multi-threading or processing of converts

From
Ddhruva <dhruva@ymail.com>
Date
Sep 16, 2008, 14:23 UTC
Message-ID
<655551.96611.qm@web95006.mail.in2.yahoo.com>
Hi,
 I am running git-p4 to import around 11147 changes from perforce, it has done 38% in 4h39m. Wonder if it would have been faster to get a bunch of changes in parallel and import them sequentially. I do understand that importing of full history does not happen too often by still it might be a good idea.
 Have a multi-threaded fetcher from source SCM and dump it in some format locally. git fast-import can pull it from the local at its own speed (which will be real fast). Basically, I am suggesting better using the available bandwidth and CPU resources for doing network IO.
-dhruva
      Cricket on your mind? Visit the ultimate cricket website. Enter http://in.sports.yahoo.com/cricket/
Message 1 of 1 in “multi-threading or processing of converts”
  1. dhruvaSep 16, 2008

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.