# Now have to wait 300 seconds after search with no results?

**URL:** <https://boards.straightdope.com/t/now-have-to-wait-300-seconds-after-search-with-no-results/469226>\
**Category:** About This Message Board\
**Created:** [October 23, 2008, 5:00pm UTC](https://boards.straightdope.com/t/now-have-to-wait-300-seconds-after-search-with-no-results/469226 "2008-10-23T17:00:48Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Revtim](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/revtim/32/1042_2.png) [@Revtim](https://boards.straightdope.com/u/Revtim)\
**Post date:** [October 23, 2008, 5:00pm UTC](https://boards.straightdope.com/t/now-have-to-wait-300-seconds-after-search-with-no-results/469226/1 "2008-10-23T17:00:48Z")

</div>

It used to be that one could search again without waiting, if the 1st search resulted in no hits. I see now one has to wait 300 seconds after a search with no results. Was this change on purpose, or is it a new bug?

---

<div class="post-metadata">

**Author:** ![Revtim](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/revtim/32/1042_2.png) [@Revtim](https://boards.straightdope.com/u/Revtim)\
**Post date:** [October 25, 2008, 1:52pm UTC](https://boards.straightdope.com/t/now-have-to-wait-300-seconds-after-search-with-no-results/469226/2 "2008-10-25T13:52:50Z")

</div>

any info on this?

---

<div class="post-metadata">

**Author:** ![Bookkeeper](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/bookkeeper/32/281_2.png) [@Bookkeeper](https://boards.straightdope.com/u/Bookkeeper)\
**Post date:** [October 25, 2008, 3:46pm UTC](https://boards.straightdope.com/t/now-have-to-wait-300-seconds-after-search-with-no-results/469226/3 "2008-10-25T15:46:40Z")

</div>

IIRC it was instituted to help work around some board slowdown issues. I don’t know if the limitation will be lifted once the current server migration and database optimization process is finished.

---

<div class="post-metadata">

**Author:** ![Revtim](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/revtim/32/1042_2.png) [@Revtim](https://boards.straightdope.com/u/Revtim)\
**Post date:** [October 26, 2008, 3:16pm UTC](https://boards.straightdope.com/t/now-have-to-wait-300-seconds-after-search-with-no-results/469226/4 "2008-10-26T15:16:42Z")

</div>

> [@Bookkeeper](#):
>
> IIRC it was instituted to help work around some board slowdown issues. I don’t know if the limitation will be lifted once the current server migration and database optimization process is finished.

Do you mean the search delay in general? I am only referring to a delay after performing a search that did not return any results. The delay after a search that returned results has been there forever, but even on the old server there was no forced delay before a new search after one that had no results.

---

<div class="post-metadata">

**Author:** ![Tenebras](https://avatars.discourse-cdn.com/v4/letter/t/977dab/32.png) [@Tenebras](https://boards.straightdope.com/u/Tenebras)\
**Post date:** [October 26, 2008, 4:19pm UTC](https://boards.straightdope.com/t/now-have-to-wait-300-seconds-after-search-with-no-results/469226/5 "2008-10-26T16:19:34Z")

</div>

And sometimes just a 300 second delay because no reason at all. About one time in three I get a five minute wait before I’ve searched for anything.

When that happens I turn on the ad blocker, because it just pisses me off.

---

<div class="post-metadata">

**Author:** ![GuanoLad](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/guanolad/32/42_2.png) [@GuanoLad](https://boards.straightdope.com/u/GuanoLad)\
**Post date:** [October 27, 2008, 10:06am UTC](https://boards.straightdope.com/t/now-have-to-wait-300-seconds-after-search-with-no-results/469226/6 "2008-10-27T10:06:07Z")

</div>

I’m almost certain that searching was never part of the site slowdown problem, there should never ever have been a slowdown problem, and it’s entirely down to incompatible and poorly implemented server settings.

---

<div class="post-metadata">

**Author:** ![Tenebras](https://avatars.discourse-cdn.com/v4/letter/t/977dab/32.png) [@Tenebras](https://boards.straightdope.com/u/Tenebras)\
**Post date:** [October 27, 2008, 4:37pm UTC](https://boards.straightdope.com/t/now-have-to-wait-300-seconds-after-search-with-no-results/469226/7 "2008-10-27T16:37:00Z")

</div>

Are you saying you doubt that a search every 30 seconds qualifies as a DOS attack? Ridiculous.

Also: we have always been at war with the board that is not to be named.

---

<div class="post-metadata">

**Author:** ![GuanoLad](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/guanolad/32/42_2.png) [@GuanoLad](https://boards.straightdope.com/u/GuanoLad)\
**Post date:** [October 27, 2008, 10:19pm UTC](https://boards.straightdope.com/t/now-have-to-wait-300-seconds-after-search-with-no-results/469226/8 "2008-10-27T22:19:23Z")

</div>

What DOS attack?

---

<div class="post-metadata">

**Author:** ![Revtim](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/revtim/32/1042_2.png) [@Revtim](https://boards.straightdope.com/u/Revtim)\
**Post date:** [October 27, 2008, 10:24pm UTC](https://boards.straightdope.com/t/now-have-to-wait-300-seconds-after-search-with-no-results/469226/9 "2008-10-27T22:24:47Z")

</div>

> [@Tenebras](#):
>
> Are you saying you doubt that a search every 30 seconds qualifies as a DOS attack? Ridiculous.

What are you talking about?

---

<div class="post-metadata">

**Author:** ![SkipMagic](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/skipmagic/32/20706_2.png) [@SkipMagic](https://boards.straightdope.com/u/SkipMagic)\
**Post date:** [October 27, 2008, 10:32pm UTC](https://boards.straightdope.com/t/now-have-to-wait-300-seconds-after-search-with-no-results/469226/10 "2008-10-27T22:32:36Z")

</div>

> [@GuanoLad](#):
>
> I’m almost certain that searching was never part of the site slowdown problem, there should never ever have been a slowdown problem, and it’s entirely down to incompatible and poorly implemented server settings.

That’s incorrect. All vBulletin boards with a certain number of posts (over a million, I think, but I don’t recall the exact number) will suffer from the same board lock-ups when searches are run. That’s why the larger boards tend to move over to a third-party search software, and that’s what Jerry’s looking [into](http://boards.straightdope.com/sdmb/showthread.php?t=482569). Searches were definitely a reason why the site occasionally grinded to a halt.

As for your original question, **Revtim** , I’ll have to defer to Jerry for the answer for when he gets the opportunity to come back and say something.

---

<div class="post-metadata">

**Author:** ![Revtim](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/revtim/32/1042_2.png) [@Revtim](https://boards.straightdope.com/u/Revtim)\
**Post date:** [October 27, 2008, 10:34pm UTC](https://boards.straightdope.com/t/now-have-to-wait-300-seconds-after-search-with-no-results/469226/11 "2008-10-27T22:34:58Z")

</div>

Thanks **SkipMagic**.

---

<div class="post-metadata">

**Author:** ![Tenebras](https://avatars.discourse-cdn.com/v4/letter/t/977dab/32.png) [@Tenebras](https://boards.straightdope.com/u/Tenebras)\
**Post date:** [October 27, 2008, 11:24pm UTC](https://boards.straightdope.com/t/now-have-to-wait-300-seconds-after-search-with-no-results/469226/12 "2008-10-27T23:24:12Z")

</div>

History. I’m talkin’ 'bout history. 🙂

**GuanoLad** said he didn’t believe the search function was the problem. The search timeout was extended to 300 seconds from 30 seconds because a member managed to crash the boards by doing 10 searches in a row, one every 30 seconds.

DOS = Denial of Service. A DOS attack is basically shutting down a website by accessing it too much, sucking all the available bandwidth so nobody else can use it. The usual method is to write a virus that will take over a couple thousand people’s computers and have them all start talking to the server at once. This then crashes the site.

At the straightdope, because of the way the search function worked, a single user acting at 30 seconds intervals knocked the whole thing to pieces on the ground.

Short version: It’s a joke, son.

---

<div class="post-metadata">

**Author:** ![GuanoLad](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/guanolad/32/42_2.png) [@GuanoLad](https://boards.straightdope.com/u/GuanoLad)\
**Post date:** [October 28, 2008, 4:24am UTC](https://boards.straightdope.com/t/now-have-to-wait-300-seconds-after-search-with-no-results/469226/13 "2008-10-28T04:24:35Z")

</div>

Well, I still am not convinced. It would then be an SQL problem, and should be solvable that way.

---

<div class="post-metadata">

**Author:** ![Spectre\_of\_Pithecanthropus](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/spectre_of_pithecanthropus/32/12343_2.png) [@Spectre\_of\_Pithecanthropus](https://boards.straightdope.com/u/Spectre_of_Pithecanthropus)\
**Post date:** [October 28, 2008, 6:37am UTC](https://boards.straightdope.com/t/now-have-to-wait-300-seconds-after-search-with-no-results/469226/14 "2008-10-28T06:37:55Z")

</div>

Shouldn’t it be possible to time the required wait for the next search with the cost of the present one? If you search a limited span of time for a subject or person, the load on the system should be relatively small, as should also be the case if you search titles only. Similarly, a negative search can still be costly to complete in terms of system resources, even though the user didn’t get any results.

---

<div class="post-metadata">

**Author:** ![ultrafilter](https://avatars.discourse-cdn.com/v4/letter/u/3d9bf3/32.png) [@ultrafilter](https://boards.straightdope.com/u/ultrafilter)\
**Post date:** [October 28, 2008, 1:31pm UTC](https://boards.straightdope.com/t/now-have-to-wait-300-seconds-after-search-with-no-results/469226/15 "2008-10-28T13:31:56Z")

</div>

Does limiting the time frame actually cut down on the work required for a search, or does it add an extra burden? It could go either way depending on how the indices are set up, and I don’t think I’ve ever seen a definitive answer.

---

<div class="post-metadata">

**Author:** ![MaceMan](https://avatars.discourse-cdn.com/v4/letter/m/4bbf92/32.png) [@MaceMan](https://boards.straightdope.com/u/MaceMan)\
**Post date:** [October 29, 2008, 6:03am UTC](https://boards.straightdope.com/t/now-have-to-wait-300-seconds-after-search-with-no-results/469226/16 "2008-10-29T06:03:32Z")

</div>

There’s a difference between a null result and a failed search. I don’t mind waiting if my search returned zero results. I do mind, however, if the search always fails due to a server-side error, and I cannot do another search for 5 minutes.

Contract or not, I am sure that a lot of knowledgeable users at the SDMB would be willing to fix these problems in short order, and for absolutely free. It’s a shame that nothing has been done in months. I do hope that extensive backups are being made for history’s sake, for when this site eventually goes down.

---

<div class="post-metadata">

**Author:** ![prisoner6655321](https://avatars.discourse-cdn.com/v4/letter/p/5f8ce5/32.png) [@prisoner6655321](https://boards.straightdope.com/u/prisoner6655321)\
**Post date:** [November 1, 2008, 6:41am UTC](https://boards.straightdope.com/t/now-have-to-wait-300-seconds-after-search-with-no-results/469226/17 "2008-11-01T06:41:49Z")

</div>

> [@MaceMan](#):
>
> I do mind, however, if the search always fails due to a server-side error, and I cannot do another search for 5 minutes.

Which is happening to me constantly. This is freaking aggravating.

Luckily I can do even more powerful searches on straightdope with Google.

---

<div class="post-metadata">

**Author:** ![Revtim](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/revtim/32/1042_2.png) [@Revtim](https://boards.straightdope.com/u/Revtim)\
**Post date:** [November 1, 2008, 3:24pm UTC](https://boards.straightdope.com/t/now-have-to-wait-300-seconds-after-search-with-no-results/469226/18 "2008-11-01T15:24:05Z")

</div>

> [@prisoner6655321](#):
>
> Luckily I can do even more powerful searches on straightdope with Google.

I tried to do a Google site search with very common terms, and came up with nothing. I assume the board is not being indexed by Google yet, how are you doing it?

---

<div class="post-metadata">

**Author:** ![prisoner6655321](https://avatars.discourse-cdn.com/v4/letter/p/5f8ce5/32.png) [@prisoner6655321](https://boards.straightdope.com/u/prisoner6655321)\
**Post date:** [November 1, 2008, 6:16pm UTC](https://boards.straightdope.com/t/now-have-to-wait-300-seconds-after-search-with-no-results/469226/19 "2008-11-01T18:16:47Z")

</div>

You have to add site:straightdope.com to the query.

[http://www.google.com/search?num=100&hl=en&rlz=1C1CHMG\_enUS291&q=obama+site:boards.straightdope.com/sdmb&btnG=Search](http://www.google.com/search?num=100&hl=en&rlz=1C1CHMG_enUS291&q=obama+site:boards.straightdope.com/sdmb&btnG=Search)

---

<div class="post-metadata">

**Author:** ![Revtim](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/revtim/32/1042_2.png) [@Revtim](https://boards.straightdope.com/u/Revtim)\
**Post date:** [November 1, 2008, 6:51pm UTC](https://boards.straightdope.com/t/now-have-to-wait-300-seconds-after-search-with-no-results/469226/20 "2008-11-01T18:51:42Z")

</div>

Huh, that’s what I thought I did, I must of screwed it up somehow. Works now for me, thanks!

[Next page](https://boards.straightdope.com/t/now-have-to-wait-300-seconds-after-search-with-no-results/469226.md?page=2)
