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

[RFC PATCH v2 2/9] merge-recursive: avoid unnecessary string list lookups

From
Elijah Newren <newren@gmail.com>
Date
Nov 20, 2017, 22:19 UTC
Message-ID
<20171120221944.15431-3-newren@gmail.com>
In-Reply-To
<20171120221944.15431-1-newren@gmail.com>

Since we're taking entries from active_cache, which is already in sorted order with same-named entries adjacent, we can skip a lookup. Also, we can just use append instead of insert (avoiding the need to find where to put the new item) and still end up with a sorted list.

Signed-off-by: Elijah Newren <newren@gmail.com>
---
 merge-recursive.c | 14 ++++++++++----
 1 file changed, 10 insertions(+), 4 deletions(-)
diff --git a/merge-recursive.c b/merge-recursive.c
index cf8986be82..09b6092abb 100644
--- a/merge-recursive.c
+++ b/merge-recursive.c
@@ -467,22 +467,28 @@ static struct stage_data *insert_stage_data(const char *path,
 static struct string_list *get_unmerged(void)
 {
 	struct string_list *unmerged = xcalloc(1, sizeof(struct string_list));
+	struct string_list_item *item;
+	const char *last = NULL;
 	int i;
 
 	unmerged->strdup_strings = 1;
 
 	for (i = 0; i < active_nr; i++) {
-		struct string_list_item *item;
 		struct stage_data *e;
 		const struct cache_entry *ce = active_cache[i];
 		if (!ce_stage(ce))
 			continue;
 
-		item = string_list_lookup(unmerged, ce->name);
-		if (!item) {
-			item = string_list_insert(unmerged, ce->name);
+		if (last == NULL || strcmp(last, ce->name)) {
+			/*
+			 * active_cache is in sorted order, so we can just call
+			 * string_list_append instead of string_list_insert and
+			 * still end up with a sorted list.
+			 */
+			item = string_list_append(unmerged, ce->name);
 			item->util = xcalloc(1, sizeof(struct stage_data));
 		}
+		last = ce->name;
 		e = item->util;
 		e->stages[ce_stage(ce)].mode = ce->ce_mode;
 		oidcpy(&e->stages[ce_stage(ce)].oid, &ce->oid);
-- 
2.15.0.323.g31fe956618
Previous: Elijah NewrenNext: Elijah Newren
Message 2 of 10 in “Improve merge recursive performance”
  1. 0/9 Improve merge recursive performanceElijah Newren, Nov 20, 2017
  2. 2/9 merge-recursive: avoid unnecessary string list lookupsElijah Newren, Nov 20, 2017
  3. 3/9 merge-recursive: new function for better colliding conflict resolutionsElijah Newren, Nov 20, 2017
  4. 1/9 diffcore-rename: no point trying to find a match better than exactElijah Newren, Nov 20, 2017
  5. 7/9 merge-recursive: improve handling for add/add conflictsElijah Newren, Nov 20, 2017
  6. 6/9 merge-recursive: improve handling for rename/rename(2to1) conflictsElijah Newren, Nov 20, 2017
  7. 4/9 Add testcases for improved file collision conflict handlingElijah Newren, Nov 20, 2017
  8. 9/9 diffcore-rename: filter rename_src list when possibleElijah Newren, Nov 20, 2017
  9. 5/9 merge-recursive: fix rename/add conflict handlingElijah Newren, Nov 20, 2017
  10. 8/9 merge-recursive: accelerate rename detectionElijah Newren, Nov 20, 2017

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.