Bug 535752 - Performance of search viewI20180924-1800

With many search results being available, the search view takes almost
all the time for refreshing the tree in the viewer. This can be avoided
since we know perfectly that there is no structural change, when calling
that method (the if insertChild() return value proves that). Therefore
instead of a structure refresh it is sufficient to update a single node
of the viewer only.

For a search with more than 500.000 results, this brings the search
runtime down from 3 minutes to 3 seconds on my system.

Change-Id: I9c80b9e2e0c6c9aaa8cc732c7eec2d76dfc55305
Signed-off-by: Michael Keppler <Michael.Keppler@gmx.de>

1 files changed, 1 insertions, 1 deletions

diff --git a/org.eclipse.search/search/org/eclipse/search/internal/ui/text/FileTreeContentProvider.java b/org.eclipse.search/search/org/eclipse/search/internal/ui/text/FileTreeContentProvider.java
index a99c9704cde..363a0485dc8 100644
--- a/org.eclipse.search/search/org/eclipse/search/internal/ui/text/FileTreeContentProvider.java
+++ b/org.eclipse.search/search/org/eclipse/search/internal/ui/text/FileTreeContentProvider.java
@@ -102,7 +102,7 @@ public class FileTreeContentProvider implements ITreeContentProvider, IFileSearc
 					fTreeViewer.add(parent, child);
 			} else {
 				if (refreshViewer)
-					fTreeViewer.refresh(parent);
+					fTreeViewer.update(parent, null);
 				return;
 			}
 			child= parent;