[GHC] #13535: vector test suite uses excessive memory on GHC 8.2

[GHC]

#13535: vector test suite uses excessive memory on GHC 8.2
-------------------------------------+-------------------------------------
        Reporter:  RyanGlScott       |                Owner:  bgamari
            Type:  bug               |               Status:  new
        Priority:  high              |            Milestone:  8.4.1
       Component:  Compiler          |              Version:  8.1
      Resolution:                    |             Keywords:
Operating System:  Unknown/Multiple  |         Architecture:
 Type of failure:  Compile-time      |  Unknown/Multiple
  performance bug                    |            Test Case:
      Blocked By:                    |             Blocking:
 Related Tickets:  #10800            |  Differential Rev(s):
       Wiki Page:                    |
-------------------------------------+-------------------------------------

Comment (by bgamari):

 Well, we have a testsuite which includes a variety of performance tests.
 However, they tend to be "microbenchmarks" are don't approach the scale of
 `vector`. Unfortunately, these tests IMHO already require far more effort
 to maintain than they give us benefit due to the need for manual bumping
 of thresholds. The problem is summarized in #12758 (which jared-w is
 working on fixing this summer).

 I do think there is room for more compiler performance tests, but I think
 they should generally be something that we monitor, not something that we
 actively need to bump thresholds on. As far as using the `vector`
 testsuite for such a testcase is concerned, I'd skeptical of including it
 wholesale. Rather, I think we would be better off building a minimized
 version of `vector`'s testcase (which will hopefully fall out naturally as
 a result of working on this ticket) and including that. Testcases with
 lots of dependencies are generally problematic as you get breakage due to
 interface changes, spurious performance fluctuations due to changes in
 dependencies, and the pain of having to track down where in your testcase
 GHC is regressing.

-- 
Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/13535#comment:39>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler