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

Re: The most efficient way to test if repositories share the same objects

From
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Date
Mar 23, 2018, 13:57 UTC
Message-ID
<179c3cf0-72bd-559a-1e00-b18ce97e8136@linuxfoundation.org>
In-Reply-To
<xmqqa7uzlr8x.fsf@gitster-ct.c.googlers.com>
On 03/22/18 17:44, Junio C Hamano wrote:
Show 14 quoted lines
> Wouldn't it be more efficient to avoid doing so one-by-one?  
> That is, wouldn't
> 
> 	rev-list --max-parents=0 --all
> 
> be a bit faster than
> 
> 	for-each-ref |
> 	while read object type refname
> 	do
> 		rev-list --max-parents=0 $refname
> 	done
> 
> I wonder?

Yeah, you're right -- I forgot that we can pass --all. The check takes 30 seconds, which is a lot better than 12 hours. :) It's a bit heavy still, but msm kernel repos are one of the heaviest outliers, so let me try to run with this.

Thanks for the suggestion!
Best,
-- 
Konstantin Ryabitsev
Director, IT Infrastructure Security
The Linux Foundation
Previous: Junio C HamanoNext: Ævar Arnfjörð Bjarmason
Message 7 of 8 in “The most efficient way to test if repositories share the same objects”
  1. Konstantin RyabitsevMar 22, 2018
  2. Ævar Arnfjörð BjarmasonMar 22, 2018
  3. Junio C HamanoMar 22, 2018
  4. Ævar Arnfjörð BjarmasonMar 22, 2018
  5. Konstantin RyabitsevMar 22, 2018
  6. Junio C HamanoMar 22, 2018
  7. Konstantin RyabitsevMar 23, 2018
  8. Ævar Arnfjörð BjarmasonMar 23, 2018

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.