Re: [67cat][ruby][code-completion] It appears that code completion info is not cached

> I just filled out a new bug report
> (http://www.netbeans.org/issues/show_bug.cgi?id=167260) and attached a
> profiler run for a single code completion.  26 seconds to display the
> dialogs.
>
> Hope this helps us clear this up.  If we can do that, then I think it
> may also fix (http://www.netbeans.org/issues/show_bug.cgi?id=160940)
> Eric M. Smith
> Burning Sun Enterprises
> http://typicalisoverrated.com
>
>
> On Wed, Jun 17, 2009 at 1:00 PM, Erno Mononen <Erno.Mononen@...
> <mailto:Erno.Mononen@...>> wrote:
>
>
>     I would love to fix the problem, but I'd really need either
>     reproducible steps or a profiler snapshot to know what to fix. If
>     I experienced the slowness myself or if anyone had filed an issue
>     for it with enough info to reproduce, the problem would be already
>     fixed. It really takes just a couple of seconds to take the
>     snapshot, see e.g.
>     http://wiki.netbeans.org/NewAndNoteworthyMilestone2NB67#section-NewAndNoteworthyMilestone2NB67-ProfileMeNow
>     for instructions. Can someone please do that and send the snapshot
>     to me?
>
>     Generally speaking, please file high priority issues for anything
>     you think is a stopper - that is the best way to make sure things
>     get fixed in a timely manner.
>
>     Thanks,
>     Erno
>
>
>     hjuskewycz wrote:
>
>         I can confirm this behavior and I have to repeat myself, the
>         Ruby code completion speed is very very poor, compared to NB 6.5.
>
>         I don't understand why? As far as I can tell the code
>         completion doesn't do much more than in NB 6.5, so why is it
>         so slow now? It is not my system, I haven't changed anything
>         compared to NB 6.5 neither has the project grown much.
>
>
>
>         I know it is just the Ruby editor, but from my perspective
>         this is a showstopper, or at least must be fixed ASAP in
>         6.7.1. Code completion was one of the main reasons NB was
>         accepted in the Ruby/Rails community, and a Java IDE hasn't a
>         very good stand there :) So please make performance on the UI
>         a top priority, like it always should be.
>
>
>
>
>
>          
>
>
>