470305 – Project refresh in Mars is much slower than Luna

Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 470305 - Project refresh in Mars is much slower than Luna

Summary: Project refresh in Mars is much slower than Luna

Status:	CLOSED DUPLICATE of bug 470153

Alias:	None

Product:	Platform
Classification:	Eclipse Project
Component:	Resources (show other bugs)
Version:	4.5
Hardware:	PC Mac OS X

Importance:	P3 major (vote)
Target Milestone:	---
Assignee:	Platform-Resources-Inbox
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2015-06-16 13:43 EDT by Dawid Pakula
Modified:	2015-06-17 04:48 EDT (History)
CC List:	1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Dawid Pakula

2015-06-16 13:43:23 EDT

I opened one of my project in fresh Mars RC4 SDK workspace (~60k resources, 1.4GB, SSD disk).

Project refresh (f5) on Luna SR2 : 2s-5s
Project refresh (f5) on Mars RC4 SDK : 60s and more

In profiler I see that everything stuck on java.io.File.list(java.io.FilenameFilter (called from org.eclipse.core.internal.filesystem.local.unix.UnixFileNatives.fetchFileInfo(String):).

I deleted all project filters and still same.

I created new project sample project (without any nature), and copy all files into it, still slow like hell.

Note: Project have couple symlinks. 
Note 2: Slowest refresh is on dirs where in one place are ~2k and more files with unknown file type. Even if they are filtered.

Oracle JDK 1.8u45

Comment 1 Szymon Ptaszkiewicz

2015-06-17 04:48:13 EDT

(In reply to Dawid Pakula from comment #0)
> In profiler I see that everything stuck on
> java.io.File.list(java.io.FilenameFilter (called from
> org.eclipse.core.internal.filesystem.local.unix.UnixFileNatives.
> fetchFileInfo(String):).

Thanks for reporting, Dawid! Based on the above information the cause is the same as in bug 470153.

*** This bug has been marked as a duplicate of bug 470153 ***