Searching...

[yanyewkay]

Previously when doing a search, if the search was unsuccessful (returned no results) I can do another search immediately. Now I have to wait 45 seconds.

I find this very cumbersome and contradicting to promoting the "search before ask" culture.

Can I have back the instant search again if no results returned feature?

[satay16]

actually, i dun really get why we even need to wait between each successful search. is it due to spamming? or does searching some how eat up bandwidth?

[ExplorerZ]

Originally Posted by satay16 actually, i dun really get why we even need to wait between each successful search. is it due to spamming? or does searching some how eat up bandwidth?

takes a lot of processing to go thru all the databases... which might lag the server if too many doing it at the same time... this is also where Google is so successful at.

[Darren]

Originally Posted by yanyewkay Previously when doing a search, if the search was unsuccessful (returned no results) I can do another search immediately. Now I have to wait 45 seconds. I find this very cumbersome and contradicting to promoting the "search before ask" culture. Can I have back the instant search again if no results returned feature?

Originally Posted by satay16 actually, i dun really get why we even need to wait between each successful search. is it due to spamming? or does searching some how eat up bandwidth?

The Search function is very taxing on the system, and is the primary reason why at peak times, the response is slower than normal.

We are exploring alternatives to the built-in search function, and hopefully, when implemented, will allow us to remove the imposed wait before doing subsequent searches.