Skip to content
Snippets Groups Projects
  1. Jan 23, 2018
    • Jan Provaznik's avatar
      Use limit for search count queries · 090ca9c3
      Jan Provaznik authored
      Search query is especially slow if a user searches a generic string
      which matches many records, in such case search can take tens of
      seconds or time out. To speed up the search query, we search only for
      first 1000 records, if there is >1000 matching records we just display
      "1000+" instead of precise total count supposing that with such amount
      the exact count is not so important for the user.
      
      Because for issues even limited search was not fast enough, 2-phase
      approach is used for issues: first we use simpler/faster query to get
      all public issues, if this exceeds the limit, we just return the limit.
      If the amount of matching results is lower than limit, we re-run more
      complex search query (which includes also confidential issues).
      Re-running the complex query should be fast enough in such case because the
      amount of matching issues is lower than limit.
      
      Because exact total_count is now limited, this patch also switches to
      to "prev/next" pagination.
      
      Related #40540
      090ca9c3
  2. Aug 24, 2017
  3. Jul 14, 2017
  4. Jul 06, 2017
  5. Jul 05, 2017
  6. May 29, 2017
  7. May 22, 2017
  8. May 08, 2017
  9. Apr 30, 2017
  10. Apr 28, 2017
  11. Apr 27, 2017
  12. Apr 14, 2017
  13. Mar 28, 2017
  14. Mar 06, 2017
  15. Feb 21, 2017
  16. Feb 16, 2017
  17. Feb 15, 2017
  18. Feb 14, 2017
  19. Feb 09, 2017
  20. Jan 24, 2017
  21. Dec 31, 2016
  22. Dec 10, 2016
  23. Nov 28, 2016
  24. Nov 16, 2016
  25. Nov 08, 2016
  26. Oct 07, 2016
  27. Sep 14, 2016
  28. Sep 05, 2016
  29. Aug 01, 2016
  30. Jun 23, 2016
  31. Jun 14, 2016
  32. Jun 03, 2016
  33. May 26, 2016
  34. May 08, 2016
  35. May 04, 2016
  36. Apr 26, 2016
Loading