Plugin is significantly slower than KeywordSuggestPlugin

[Ryan J Ollos]

Using KeywordSuggestPlugin as a metric, it seems like we should be able to make this plugin more responsive.

-----Original Message-----
From: Steffen Hoffmann
Sent: Tuesday, August 31, 2010 11:00
To: Ryan Ollos
Subject: Re: Trac developer discussion - was: Re: Re2: regarding
WikiTicketCalendarMacro display width control

> KeywordSuggest is very fast to bring up the list of suggestions from
> a list of several hundred tags. AutocompleteUsers on the other hand
> is not very responsive, and takes 1-3 seconds to make suggestions
> from a list of 15 users. If you are seeing this same behavior, I'll
> start looking at the code and see if we can optimize it somehow. If
> not, perhaps it has something more to do with my Trac installation.

Right, see this as well. Even worse, the AutocompleteUsers sometimes
stopped work at all. Not done too much research on the matter, but I
remember having seen all currently available keywords packed into a list
plus a JS function in the header of HTML pages. While the lookup is done
in the local browser instance, AutocompleteUsers will certainly do
different, so bound to be slower and seemingly more complicated.

[Ryan J Ollos]

Changing ticket owner to be new maintainer.

[Grzegorz Sobański]

KeywordSuggestPlugin works in different way, so it so more responsive.

KeywordSuggestPlugin embedes into the ticket page a list of suggestions, this plugin makes ajax requests to get the matching users. So it won't ever have the same responsivenes.