« Return to Thread: [67cat] Project scan issues.
Re: [67cat] Project scan issues.
by esmithbss
::
Rate this Message:
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
>>
>
>
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
>>
>
>
« Return to Thread: [67cat] Project scan issues.
| Free embeddable forum powered by Nabble | Forum Help |
