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

git-diff-tree -M performance regression in 'next'

From
Fredrik Kuivinen <freku045@student.liu.se>
Date
Mar 11, 2006, 17:28 UTC
Message-ID
<20060311172818.GB32609@c165.ib.student.liu.se>
Hi,

I added some time logging code to git-merge-recursive to see exactly what we spend all the time on in merges which involves many changes, such as a merge of a slightly modified v2.6.12 and an unmodified v2.6.15.

I turned out that the rename detection took almost 10 minutes on my machine. More specifically,

   git-diff-tree -r -M --diff-filter=R v2.6.12 v2.6.14
takes ~9 minutes with the current 'next'.

With 65416758cd83772f2f3c69f1bd1f501608e64745, which uses the delta code to compute the similarity measure, the above git-diff-tree invocation takes 1.50 minutes.

- Fredrik
Next: Junio C Hamano
Message 1 of 17 in “git-diff-tree -M performance regression in 'next'”
  1. Fredrik KuivinenMar 11, 2006
  2. Junio C HamanoMar 12, 2006
  3. Junio C HamanoMar 12, 2006
  4. Linus TorvaldsMar 12, 2006
  5. Junio C HamanoMar 12, 2006
  6. Junio C HamanoMar 13, 2006
  7. Linus TorvaldsMar 13, 2006
  8. Junio C HamanoMar 13, 2006
  9. Linus TorvaldsMar 13, 2006
  10. Linus TorvaldsMar 13, 2006
  11. Linus TorvaldsMar 13, 2006
  12. Linus TorvaldsMar 13, 2006
  13. Linus TorvaldsMar 13, 2006
  14. Junio C HamanoMar 13, 2006
  15. Junio C HamanoMar 14, 2006
  16. Linus TorvaldsMar 14, 2006
  17. Junio C HamanoMar 14, 2006

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.