Run GC every 2s rather than 0.3s

[begriffs]

Fixes #565

[begriffs]

Looks like cabal check is confusing the RTS option with a ghc-option:

stack exec -- cabal check
The following warnings are likely affect your build negatively:
* Instead of 'ghc-options: -I2"' use 'include-dirs: 2"'

Hackage would reject this package.

Or maybe grouped quoted options is not valid in a cabal file. I'll consult the docs...

[begriffs]

This builds and passes cabal check. Looking at its eventlog the GC doesn't run much as I use the program. Although going back to the original rtsopts the GC didn't seem to run much either.

Also if I change it to "-with-rtsopts=-N -K8" it will not crash the program whereas running with +RTS -K8 -RTS will. So I'm not sure it's actually using this configuration.

[begriffs]

Turns out I had to run stack clean for the rtsopts to take effect in a new build. Merging.

[eric-brechemier]

Turns out I had to run stack clean for the rtsopts to take effect in a new build. (...)

Is it required to run stack clean for those of us building PostgREST from source?

[ruslantalpa]

my guess is yes

On Thu, May 26, 2016 at 3:42 PM, Eric Bréchemier notifications@github.com
wrote:

Turns out I had to run stack clean for the rtsopts to take effect in a
new build. Merging.

Is it required for those of us building PostgREST from source?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#604 (comment)

[begriffs]

To pick up changed GHC flags it's better to clean to be on the safe side.