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

Proposal: Output should push to different servers in parallel

From
Victor Porton <porton@narod.ru>
Date
Feb 6, 2019, 22:33 UTC
Message-ID
<173ed6e2-7f33-62a0-e1bd-f4663e68490e@narod.ru>
I experienced a slowdown in Git pushing when I push to more than one server.
I propose:
Run push to several servers in parallel.

Not to mix the output, nevertheless serialize the output, that is for example cache the output of the second server push and start to output it immediately after the first server push is finished.

This approach combines the advantages of the current way (I suppose it is so) to serialize pushes: first push to the first server, then to the second, etc. and of my idea to push in parallel.

I think the best way would be use multithreading, but multiprocessing would be a good quick solution.

Next: Ævar Arnfjörð Bjarmason
Message 1 of 3 in “Proposal: Output should push to different servers in parallel”
  1. Victor PortonFeb 6, 2019
  2. Ævar Arnfjörð BjarmasonFeb 7, 2019
  3. Junio C HamanoFeb 7, 2019

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.