Yes, I was trying to reduce the amount of time spent on ranking objects by preventing the search from happening if there were more keystrokes coming (aka the user types "itunes", it prevents searching "i", then "it", then "itu", then..., which uses CPU for almost nothing more). I'm lowering the threshold from 0.333s to 0.150 for the next version.
Etienne. Le 14 mars 09 à 16:19, Reza Jelveh a écrit :
btw im not sure if it's related but as i recall there was some "optimizations" to the search result set in the a5, right?
