1031995 - Slow searches cause timeouts

Status: RESOLVED WORKSFORME

(Socorro :: General, task)

Description

[(Away)]

https://crash-stats.mozilla.com/search/?date=%3E%3D6%2F20%2F2014&date=%3C6%2F21%2F2014&build_id=%3E%3D20140610000123&build_id=%3C20140611000456&dump=~libinject2.dll&_facets=signature&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform

Change the ...123 and ...456 on the build IDs, to make sure your search hasn't been cached.

Expected result: Search results, eventually.

Actual result: Progress bar for a while, then error. Wait, reload, and then it works.

Comment 1

[Lonnen :lonnen]

Interesting that it's available from the cache next time. We could probably implement a more sophisticated timeout behavior.

Comment 2

[Robert Kaiser]

I've seen the same kind of behavior with https://crash-stats.mozilla.com/topcrasher_ranks_bybug/?bug_number=1023239 today (not a search, but topcrasher_ranks_bybug is prone to run long, esp. with multiple signatures): It timed out, and after a reload, it was fine and fast coming out of the cache.

Comment 3

[(Away)]

It has gotten worse: now, when I try reloading the query a few minutes later, I just get "No results were found" for any search involving the dump field.

Did something recently change?

Comment 4

[Lonnen :lonnen]

I've skimmed the change log for the last two weeks and nothing is jumping out at me. Can you give me examples?

Comment 5

[(Away)]

Well, it's working (*) again. Must be one of those issues that stops reproducing when a developer looks at it. Fun times.

(*) By "working" I mean there's still a timeout, but I can reload after a while and get the results.

Comment 6

[Peter Bengtsson [:peterbe]]

In the last year we've made a huge improvement to the SuperSearch in that we only pull down columns we will actually display. This has boosted it significantly. 

David, we might still have performance issues on SuperSearch but it should have improved significantly in the last 12 months. Wanna close this bug?