First thing that comes to mind is memory. Is there enough system memory (or are you swapping) and is QS using a lot (say something large on the clipboard)?
Howard On Jun 14, 2010, at 4:12 PM, sclough wrote: > Yea, I'd love to know if there's anything that can be done to help > it... > > On Jun 14, 1:35 am, huiii <[email protected]> wrote: >> i got the same problem since snow leopard, and the same question... >> >> On Jun 13, 4:28 pm, sclough <[email protected]> wrote: >> >> >> >>> I've noticed periodically when I invoke QS, that there seems to be a >>> hesitation for a few seconds before it responds to my input. The >>> command window comes up, but it just doesn't respond. For example, if >>> I'm activating an application I can invoke QS, type in the characters >>> needed, and hit enter to active the app before QS even displays that >>> app in the UI. Since QS has learned what I want, I just type and go >>> even though I'm not getting any visual feedback. When I do this it >>> seems like there's a pause when I hit enter as QS updates the UI to >>> display the icon that matches what I typed before it actually launches >>> or actives it. Hopefully this makes sense. Anyway, I'm wondering if >>> there's anything that can be done to help this? I've thought about >>> trying to replace my catalog entirely with spotlight sources in case >>> refreshing the catalog is the issue, although I would assume that's >>> something done in the background that shouldn't affect the ui. I can't >>> think of much else that I could tweak beyond reducing the number of >>> catalog items, but my catalog isn't massive (probably around 1,500 >>> items including address book, files, and everything). Any ideas about >>> what's causing this and what I could do to improve performance?
