id	summary	reporter	owner	description	type	status	priority	component	severity	resolution	keywords	cc	release
7605	Plugin is significantly slower than KeywordSuggestPlugin	rjollos	rjollos	Using KeywordSuggestPlugin as a metric, it seems like we should be able to make this plugin more responsive.\r\n\r\n{{{\r\n#!email\r\n-----Original Message-----\r\nFrom: Steffen Hoffmann\r\nSent: Tuesday, August 31, 2010 11:00\r\nTo: Ryan Ollos\r\nSubject: Re: Trac developer discussion - was: Re: Re2: regarding WikiTicketCalendarMacro display width control\r\n\r\n> KeywordSuggest is very fast to bring up the list of suggestions from\r\n> a list of several hundred tags. AutocompleteUsers on the other hand\r\n> is not very responsive, and takes 1-3 seconds to make suggestions\r\n> from a list of 15 users. If you are seeing this same behavior, I'll\r\n> start looking at the code and see if we can optimize it somehow. If\r\n> not, perhaps it has something more to do with my Trac installation.\r\n\r\nRight, see this as well. Even worse, the AutocompleteUsers sometimes\r\nstopped work at all. Not done too much research on the matter, but I\r\nremember having seen all currently available keywords packed into a list\r\nplus a JS function in the header of HTML pages. While the lookup is done\r\nin the local browser instance, AutocompleteUsers will certainly do\r\ndifferent, so bound to be slower and seemingly more complicated.\r\n}}}	defect	new	normal	AutocompleteUsersPlugin	normal			hasienda	0.11