<…> I make one search and the whole system is down for 10 minutes lol
You’d really need to be more specific, stating enough information for the admin/people to be able to reproduce the exact case (i.e. search string, browser, exact message returned (*), type of device, is it a recurrent error tested on different occasions, etc.).
I use the search function frequently without any issue whatsoever, although I always use the
advanced search function in order to parametrize the query (i.e. delimit time interval, sort order, etc.).
(*):
The error message goes somewhere along the lines of:
An Error Has Occurred!
You are searching too quickly. Wait 4 seconds. (There is a Google-based search engine on the search page that does not have this limit.)
It should state a waiting period that depends on your Activity, ranging from 360 seconds to 4 seconds:
<…>
waittime = 360;
if(activity >= 15)
waittime = (int)(90 - activity);
if(activity >= 60)
waittime=(int)(34.7586 - (0.0793103 * activity));
if(activity >= 100)
waittime = max((int)(14-(activity/50)), 4);
Since your Activity is currently 749, your waittime between searches should be of 4 seconds. That is, unless there are network issues on either end or you just happened to catch a minor point in time server hiccup.