Bug 168536 – Invoking Open Project took 45,800 ms.

HOME \ Community

Bug 168536 - Invoking Open Project took 45,800 ms.

Summary:

Invoking Open Project took 45,800 ms.

Status:	VERIFIED FIXED

Product:	editor
Component:	Settings
Version:	6.8
Platform:	All All

Priority:	P3 (vote)
Target Milestone:	6.8
Assigned To:	issues@editor
QA Contact:	issues@editor

URL:	http://statistics.netbeans.org/except...
Whiteboard:	EXCEPTIONS_REPORT perf-profileme
Keywords:

Depends on:	161201
Blocks:
	Show dependency tree / graph

Reported:	2009-07-14 11:37 by Jindrich Sedek
Modified:	2009-09-03 21:44 (History)

Issue Type:	DEFECT
Exception Reporter :

Attachments
nps snapshot (84.80 KB, bin/nps) 2009-07-14 11:37, Jindrich Sedek	Details
nps snapshot (25.39 KB, bin/nps) 2009-07-21 12:57, Martin Schovanek	Details
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 From Jindrich Sedek 2009-07-14 11:37:25

Build: NetBeans IDE Dev (Build 200907130200)
VM: Java HotSpot(TM) 64-Bit Server VM, 14.0-b16, Java(TM) SE Runtime
Environment, 1.6.0_14-b08
OS: Linux, 2.6.27.25-170.2.72.fc10.x86_64, amd64

User Comments:
jsedek: I had opened pom maven project and I was opening web project embedded
in the original one


Maximal alredy reported slowness was 45800 ms, average is 45800

------- Comment #1 From Jindrich Sedek 2009-07-14 11:37:30 -------

Created an attachment (id=84697) [details]
nps snapshot

------- Comment #2 From Jaroslav Tulach 2009-07-14 12:49:46 -------

*** Issue 168056 has been marked as a duplicate of this issue. ***

------- Comment #3 From Petr Jiricka 2009-07-14 12:53:18 -------

See also:
http://www.nabble.com/-67cat---other--NetBeans-6.7-Final-tt24252984.html

------- Comment #4 From Vitezslav Stejskal 2009-07-14 15:27:45 -------

AFAIR I was making some fixes around this area. There is a huge number of
events fired from filesystems that all make
MimeLookup to recalculate its contents. These events are fired from an
AtomicAction, so they really come in one huge
bundle. Unfortunately it's not possible to recognize this from the API client's
side, ie. one does not know that there
is the whole lump of events coming and so can't do the refresh only once.
Instead each event is delivered separately and
triggers the refresh again and again. A possible solution could be to use a
sliding task (an async task) that is
(re)scheduled when an event arrives and that does the refresh. The drawback is
that its asynchronous...

------- Comment #5 From Vitezslav Stejskal 2009-07-16 17:24:11 -------

http://hg.netbeans.org/jet-main/rev/df4e2c88c39d

------- Comment #6 From qa 2009-07-20 09:49:29 -------

Integrated into 'main-golden', will be available in build *200907200201* on
http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main-golden/rev/df4e2c88c39d
User: Vita Stejskal <vstejskal@netbeans.org>
Log: #168536: hopefully better algorithm for coalescing filesystem events

------- Comment #7 From Martin Schovanek 2009-07-21 12:57:13 -------

Build: NetBeans IDE Dev (Build 200907210201)
VM: Java HotSpot(TM) 64-Bit Server VM, 11.3-b02-83, Java(TM) SE Runtime
Environment, 1.6.0_13-b03-211
OS: Mac OS X, 10.5.7, x86_64

User Comments: 

Maximal alredy reported slowness was 45800 ms, average is 12643

------- Comment #8 From Martin Schovanek 2009-07-21 12:57:17 -------

Created an attachment (id=84999) [details]
nps snapshot

------- Comment #9 From Jindrich Sedek 2009-07-27 10:34:59 -------

verified.
NetBeans IDE Dev (Build 200907270201)

------- Comment #10 From Vitezslav Stejskal 2009-09-03 21:44:44 -------

Please also see the latest comments in issue #161201.