|
View:
New views
20 Messages
—
Rating Filter:
Alert me
|
| < Prev | 1 - 2 | Next > |
|
|
[67cat] Project scan issues.Are other people finding the project scans and navigation slow or is this just me ? When I open a Java file for the first time it can take 60+ seconds for the navigation to be available. As developers tend to bounce around a number of files this can be a real issue. I have seen a number of other users complaining about this on the user forums. See bug#161367 (http://www.netbeans.org/issues/show_bug.cgi?id=161367) Attachments: http://forums.netbeans.org//files/nb_110.png |
|
|
Re: [67cat][core] Project scan issues.I'm working with Grails projecs and navigation window is sometimes 2-3
files "behind" when switching between files. Yesterday I got so irritated I closed it. I think the thread that build the navigation window should be killed immediately when you switch to another file. Why keep on scanning when I no longer are looking at the file? /Goran Ehrsson nleck wrote: > Are other people finding the project scans and navigation slow or is this just me ? > > > > When I open a Java file for the first time it can take 60+ seconds for the navigation to be available. As developers tend to bounce around a number of files this can be a real issue. > > > > I have seen a number of other users complaining about this on the user forums. > > > > See bug#161367 (http://www.netbeans.org/issues/show_bug.cgi?id=161367) > > > > > Attachments: > http://forums.netbeans.org//files/nb_110.png > > > |
|
|
Re: [67cat][core] Project scan issues.Am 25.05.2009 11:02, Goran Ehrsson schrieb:
> I'm working with Grails projecs and navigation window is sometimes 2-3 > files "behind" when switching between files. Yesterday I got so > irritated I closed it. > I think the thread that build the navigation window should be killed > immediately when you switch to another file. Why keep on scanning > when I no longer are looking at the file? +1 Additionally I agree with nleck. -Ulf > > /Goran Ehrsson > > nleck wrote: >> Are other people finding the project scans and navigation slow or is >> this just me ? >> >> >> When I open a Java file for the first time it can take 60+ seconds >> for the navigation to be available. As developers tend to bounce >> around a number of files this can be a real issue. >> >> >> I have seen a number of other users complaining about this on the >> user forums. >> >> >> >> See bug#161367 (http://www.netbeans.org/issues/show_bug.cgi?id=161367) >> >> >> >> >> Attachments: http://forums.netbeans.org//files/nb_110.png >> >> >> > > |
|
|
RE: [67cat][core] Project scan issues.+1
--nm > -----Original Message----- > From: Ulf Zibis [mailto:Ulf.Zibis@...] > Sent: Mon, 25. May 2009 15:03 > To: netcat@... > Subject: Re: [67cat][core] Project scan issues. > > Am 25.05.2009 11:02, Goran Ehrsson schrieb: > > I'm working with Grails projecs and navigation window is > sometimes 2-3 > > files "behind" when switching between files. Yesterday I got so > > irritated I closed it. > > I think the thread that build the navigation window should > be killed > > immediately when you switch to another file. Why keep on scanning > > when I no longer are looking at the file? > > +1 > > Additionally I agree with nleck. > > -Ulf > > > > > /Goran Ehrsson > > > > nleck wrote: > >> Are other people finding the project scans and navigation > slow or is > >> this just me ? > >> > >> > >> When I open a Java file for the first time it can take 60+ seconds > >> for the navigation to be available. As developers tend to bounce > >> around a number of files this can be a real issue. > >> > >> > >> I have seen a number of other users complaining about this on the > >> user forums. > >> > >> > >> > >> See bug#161367 > (http://www.netbeans.org/issues/show_bug.cgi?id=161367) > >> > >> > >> > >> > >> Attachments: http://forums.netbeans.org//files/nb_110.png > >> > >> > >> > > > > > > |
|
|
Re: [67cat] Project scan issues.Additionally I think, collapsing comments etc. in the editor should be
done first (before updating navigation), so user could start editing immediately. -Ulf Am 24.05.2009 03:46, nleck schrieb: > Are other people finding the project scans and navigation slow or is this just me ? > > > > When I open a Java file for the first time it can take 60+ seconds for the navigation to be available. As developers tend to bounce around a number of files this can be a real issue. > > > > I have seen a number of other users complaining about this on the user forums. > > > > See bug#161367 (http://www.netbeans.org/issues/show_bug.cgi?id=161367) > > > > > Attachments: > http://forums.netbeans.org//files/nb_110.png > > > > |
|
|
Re: [67cat] Project scan issues.Trying out RC1 and I've never had this before but now I'm having scanning slowness constantly and goto source as well as refactoring.
On Wed, May 27, 2009 at 7:33 PM, Ulf Zibis <Ulf.Zibis@...> wrote: Additionally I think, collapsing comments etc. in the editor should be done first (before updating navigation), so user could start editing immediately. |
|
|
Re: [67cat] Project scan issues.I also experienced the slowness when I use NB for my project.
Thousands of java and jsp files and libraries..., and it takes several minutes to be ready. BR Sun Kim 2009/6/2 Aaron Hagopian <airhead1@...> Trying out RC1 and I've never had this before but now I'm having scanning slowness constantly and goto source as well as refactoring. -- Thanks and best regards, Sun Kim |
|
|
Re: [67cat] Project scan issues.I tried to get a call graph and I got the "please wait" message.. the status bar said that scanning was in progress.. I waited (way too long) and the scanning message went away from the status bar. But the call graph window was still saying "please wait" - It appeared that nothing was happening.
I closed the call graph window and tried again - boom instantly the call graph was there. The "scanning" delays combined with a failure for some things to update when the scanning finishes is really going to hurt. I'm with the others, scanning takes orders of magnitude longer than it should. I can compile my project in less time. In general I see "please wait" too often and for too long. That's my main complaint.. in other areas I'm quite happy with how things are working. (Well I still fight the GUI layout tool on a daily basis :-) ) Scott On 1-Jun-09, at 7:42 PM, HakSun Kim wrote: I also experienced the slowness when I use NB for my project. |
|
|
Re: [67cat] Project scan issues.The project scanning does take a lot of time and is painful when you rely on externally built libraries.
Everytime I built an external library and replace it in the lib folder te sacanning is triggered. It also happens everytime I start the IDE. I always thought the scanning results should be saved and updated only when something changes and always thought that is how it is implemented, but it doesn't seem so. :(
The diamond cannot be polished without friction, nor man perfected without trials http://mytechrantings.blogspot.com On Tue, Jun 2, 2009 at 8:08 AM, Scott Palmer <swpalmer@...> wrote:
|
|
|
Re: [67cat] Project scan issues.I've seen this too. It's a bit late to do this, but it seems like the
solution would be to cache the scan results in the nbproject/private folder with a checksum key, then when NB opens it can do a quick checksum computation. If they match it loads the cached data. If not, it has to scan. This could even be taken 1 step further with each file having a checksum as well. Update the checksum during file save and your set. Even if you only get the file saved and the checksum doesn't make it to disk during a power down or something similar, it shouldn't break the optimization. It's a bit of an obvious solution, and probably been bantered about a bit already, but it could easily take care of half if not more of the scanning speed issues. Eric M. Smith Rohit Rai wrote: > The project scanning does take a lot of time and is painful when you > rely on externally built libraries. > Everytime I built an external library and replace it in the lib folder > te sacanning is triggered. > > It also happens everytime I start the IDE. I always thought the > scanning results should be saved and updated only when something > changes and always thought that is how it is implemented, but it > doesn't seem so. :( > > The diamond cannot be polished without friction, nor man perfected > without trials > http://mytechrantings.blogspot.com > > > On Tue, Jun 2, 2009 at 8:08 AM, Scott Palmer <swpalmer@... > <mailto:swpalmer@...>> wrote: > > I tried to get a call graph and I got the "please wait" message.. > the status bar said that scanning was in progress.. I waited (way > too long) and the scanning message went away from the status bar. > But the call graph window was still saying "please wait" - It > appeared that nothing was happening. > I closed the call graph window and tried again - boom instantly > the call graph was there. > > The "scanning" delays combined with a failure for some things to > update when the scanning finishes is really going to hurt. > > I'm with the others, scanning takes orders of magnitude longer > than it should. I can compile my project in less time. In > general I see "please wait" too often and for too long. > > That's my main complaint.. in other areas I'm quite happy with how > things are working. (Well I still fight the GUI layout tool on > a daily basis :-) ) > > Scott > > > On 1-Jun-09, at 7:42 PM, HakSun Kim wrote: > >> I also experienced the slowness when I use NB for my project. >> Thousands of java and jsp files and libraries..., and it takes >> several minutes to be ready. >> >> BR >> Sun Kim >> >> 2009/6/2 Aaron Hagopian <airhead1@... >> <mailto:airhead1@...>> >> >> Trying out RC1 and I've never had this before but now I'm >> having scanning slowness constantly and goto source as well >> as refactoring. >> >> >> >> On Wed, May 27, 2009 at 7:33 PM, Ulf Zibis <Ulf.Zibis@... >> <mailto:Ulf.Zibis@...>> wrote: >> >> Additionally I think, collapsing comments etc. in the >> editor should be done first (before updating navigation), >> so user could start editing immediately. >> >> -Ulf >> >> >> Am 24.05.2009 03:46, nleck schrieb: >> >> Are other people finding the project scans and >> navigation slow or is this just me ? >> >> >> When I open a Java file for the first time it can >> take 60+ seconds for the navigation to be available. >> As developers tend to bounce around a number of files >> this can be a real issue. >> >> >> I have seen a number of other users complaining about >> this on the user forums. >> >> >> >> See bug#161367 >> (http://www.netbeans.org/issues/show_bug.cgi?id=161367) >> >> >> >> >> Attachments: http://forums.netbeans.org//files/nb_110.png >> > > |
|
|
[67cat] Project scan issues. |
|
|
Re: [67cat][groovy] Project scan issues.Here's my first observation with jet-main-755-on-090602
1. Removed .netbeans user dir. 2. Installed above NB build. 3. Opened a Grails project with 45 domains and 50 controllers. 4. Waited 40 minutes! for Project Scan to complete. I'm now using this build for grails development today. I will report more if I see something odd. /Goran Ehrsson |
|
|
Re: [67cat] Project scan issues.I have filed an issue:
http://www.netbeans.org/issues/show_bug.cgi?id=166668 -Ulf Am 28.05.2009 02:33, Ulf Zibis schrieb: > Additionally I think, collapsing comments etc. in the editor should be > done first (before updating navigation), so user could start editing > immediately. > > -Ulf > > > Am 24.05.2009 03:46, nleck schrieb: >> Are other people finding the project scans and navigation slow or is >> this just me ? >> >> >> When I open a Java file for the first time it can take 60+ seconds >> for the navigation to be available. As developers tend to bounce >> around a number of files this can be a real issue. >> >> >> I have seen a number of other users complaining about this on the >> user forums. >> >> >> >> See bug#161367 (http://www.netbeans.org/issues/show_bug.cgi?id=161367) >> >> >> >> >> Attachments: http://forums.netbeans.org//files/nb_110.png >> >> >> >> > > |
|
|
[67cat] Project scan issues.This seems to be a direct flow on from the previous fix. compare 6.5:- http://www.netbeans.org/nonav/issues/showattachment.cgi/83269/nb_scan-6.5.ogg and 6.7 :- http://www.netbeans.org/nonav/issues/showattachment.cgi/83267/nb_scan.ogg Releasing NB with a performance regression will be very bad. |
|
|
Re: [67cat] Project scan issues.I'm stuck when I start NetBeans 6.7 because of a project that contains about 134000 files.
However, when I try same project in Eclipse, it is better. The eclipse doesn't freeze. This is critical for me at this time, cause this is my major project. I really hope to use NB for my project. Please help!!! 2009/6/8 nleck <nleck@...>
-- Thanks and best regards, Sun Kim |
|
|
Re: [67cat] Project scan issues.Hi HakSun,
we are still working on NB 6.7 and trying to fix the most critical and annoying cases when user faces unnecessary scan. I would like to ask you for help, could you please share the project you are speaking about for internal testing purposes with NetBeans team ? This will definitely help us to address problems you are facing. Thanks in advance, *Marian HakSun Kim wrote: > I'm stuck when I start NetBeans 6.7 because of a project that contains > about 134000 files. > However, when I try same project in Eclipse, it is better. The eclipse > doesn't freeze. > This is critical for me at this time, cause this is my major project. > I really hope to use NB for my project. Please help!!! > > 2009/6/8 nleck <nleck@... <mailto:nleck@...>> > > > This seems to be a direct flow on from the previous fix. > > > > compare 6.5:- > > > http://www.netbeans.org/nonav/issues/showattachment.cgi/83269/nb_scan-6.5.ogg > > and 6.7 :- > > > http://www.netbeans.org/nonav/issues/showattachment.cgi/83267/nb_scan.ogg > > > > > > Releasing NB with a performance regression will be very bad. > > > > > > > > > -- > Thanks and best regards, > Sun Kim |
|
|
[67cat] Project scan issues.Please see bug#167399 (http://www.netbeans.org/issues/show_bug.cgi?id=167399) I really don't think we should release with know performance regressions. 6.5 performance was bad when compared to Eclipse and now 6.7 will be worst. |
|
|
RE: [67cat] Project scan issues.I agree, but I'm not holding my breath.
Getting up to Eclipse performance levels for project scanning and code editing/navigation/completion should really be priority #1 for 6.8, though. In the current state it's almost impossible to get someone used to Eclipse to use NetBeans, and NetBeans users are prone to jump ship due to these performance issues with NB 6.x that are getting worse from release to release. -- Niklas Matthies On Tue, 23. Jun 2009 01:56, nleck wrote: > Please see bug#167399 > (http://www.netbeans.org/issues/show_bug.cgi?id=167399) > > > > I really don't think we should release with know performance > regressions. 6.5 performance was bad when compared to Eclipse > and now 6.7 will be worst. |
|
|
RE: [67cat] Project scan issues.+1
- Performance ("Scanning...", "Please wait", "what happened to the Navigation window?") - Stability (how many NPEs have encountered?) - Correctness (error badges, debugger display values) ... are the main "problems" with NetBeans. Fluff like Kenai integration may make for a neat demo, but it is 100% useless to me in my day job doing closed-source projects that actually make money ;-) It's not that I don't appreciate many of the new features.. but performance has been significantly behind the competition for years. It's time to catch up. Scott > -----Original Message----- > From: Matthies, Niklas [mailto:niklas.matthies@...] > Sent: June 23, 2009 10:33 AM > To: netcat@... > Subject: RE: [67cat] Project scan issues. > > I agree, but I'm not holding my breath. > > Getting up to Eclipse performance levels for project scanning and code > editing/navigation/completion should really be priority #1 for 6.8, > though. In the current state it's almost impossible to get someone > to Eclipse to use NetBeans, and NetBeans users are prone to jump ship > due to these performance issues with NB 6.x that are getting worse from > release to release. > > -- Niklas Matthies > > > On Tue, 23. Jun 2009 01:56, nleck wrote: > > Please see bug#167399 > > (http://www.netbeans.org/issues/show_bug.cgi?id=167399) > > > > > > > > I really don't think we should release with know performance > > regressions. 6.5 performance was bad when compared to Eclipse > > and now 6.7 will be worst. |
|
|
Re: [67cat] Project scan issues.Hi everyone,
you can help us by submitting a bug reports on this - I have already posted this blog post many times but I guess it is never enough: http://blogs.sun.com/joshis/entry/netbeans_ide_is_scanning_parsing It describe what specific things you need to do in order to submit a useful bug report on scanning... With regards, Petr Dvorak Rohit Rai wrote: > +1 > > As I said, we should have a release dedicated to performance > improvements. Eclipse has done it in early days once, I remember > around 3-4 year back. > > > The diamond cannot be polished without friction, nor man perfected > without trials > http://mytechrantings.blogspot.com > > > On Wed, Jun 24, 2009 at 10:13 AM, HakSun Kim <glarian@... > <mailto:glarian@...>> wrote: > > +1 > > 2009/6/24 Anuradha G <theanuradha@... > <mailto:theanuradha@...>> > > +1 > > > On Tue, Jun 23, 2009 at 8:45 PM, Scott Palmer > <Scott@... <mailto:Scott@...>> > wrote: > > +1 > - Performance ("Scanning...", "Please wait", "what > happened to the > Navigation window?") > - Stability (how many NPEs have encountered?) > - Correctness (error badges, debugger display values) > ... are the main "problems" with NetBeans. > > Fluff like Kenai integration may make for a neat demo, but > it is 100% > useless to me in my day job doing closed-source projects > that actually > make money ;-) > It's not that I don't appreciate many of the new > features.. but > performance has been significantly behind the competition > for years. > It's time to catch up. > > Scott > > > > -----Original Message----- > > From: Matthies, Niklas > [mailto:niklas.matthies@... > <mailto:niklas.matthies@...>] > > Sent: June 23, 2009 10:33 AM > > To: netcat@... <mailto:netcat@...> > > Subject: RE: [67cat] Project scan issues. > > > > I agree, but I'm not holding my breath. > > > > Getting up to Eclipse performance levels for project > scanning and code > > editing/navigation/completion should really be priority > #1 for 6.8, > > though. In the current state it's almost impossible to > get someone > used > > to Eclipse to use NetBeans, and NetBeans users are prone > to jump ship > > due to these performance issues with NB 6.x that are > getting worse > from > > release to release. > > > > -- Niklas Matthies > > > > > > On Tue, 23. Jun 2009 01:56, nleck wrote: > > > Please see bug#167399 > > > (http://www.netbeans.org/issues/show_bug.cgi?id=167399) > > > > > > > > > > > > I really don't think we should release with know > performance > > > regressions. 6.5 performance was bad when compared to > Eclipse > > > and now 6.7 will be worst. > > > > > -- > Anuradha G > > > > > -- > Thanks and best regards, > Sun Kim > >
My websites:
English: http://wiki.netbeans.org/PetrDvorak
English: http://blogs.sun.com/joshis
Czech: http://joshis.iprofil.cz/
|
| < Prev | 1 - 2 | Next > |
| Free embeddable forum powered by Nabble | Forum Help |