Closed Bug 1184000 Opened 10 years ago Closed 9 years ago

Slow search performance

Categories

(Mozilla QA Graveyard :: MozTrap, defect)

42 Branch
defect
Not set
major

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: mau8345, Unassigned, Mentored)

References

Details

User Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:42.0) Gecko/20100101 Firefox/42.0 Build ID: 20150714030206 Steps to reproduce: The performance of search and the search suggestions is extremely slow. To replicate: 1. Go to https://moztrap.allizom.org/results/cases/ 2. Print '"testrun" into search field Actual results: Extremely slow search. Expected results: Should search much faster. See the bug N 773302 - Slow searching performance
Severity: normal → major
Priority: -- → P2
Mentor: rbillings
I am able to reproduce this issue: Browser: Firefox 42.0, Safari Versión 9.0.1 OS: X El Capitan Version: 10.11.1 Reproduction steps: Go to "https://moztrap.allizom.org/results/cases/" Type the world "test" in the search box. Current result The text box is block during few seconds, I am not able to type the complete word "test". Expected result Search should be faster
The dealy time varies. But it's only a few seconds for me
Priority: P2 → --
See Also: → 773302
Mass-closing remaining MozTrap bugs as WONTFIX, due to 1) the Mozilla-hosted instance being decommissioned (see https://wiki.mozilla.org/TestEngineering/Testrail), and, for now, 2) the still-up code archived at its GitHub page: https://github.com/mozilla/moztrap (we'll decide what's next for that, in the near future). See also the history and more-detailed discussion which led us here, at https://groups.google.com/forum/#!topic/mozilla.dev.quality/Sa75hV8Ywvk (If you'd like, you should be able to filter these notification emails using at least the unique string of "Sa75hV8Ywvk" in the message body. Thanks!
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in before you can comment on or make changes to this bug.