GHC has a "stop the world" garbage collector, meaning that while major GC is happening, the entire process must be halted. In my experience GC pause times are typically low, but depending the heap residency profile of your application (and the quantity of garbage being produced by it), this may not be the case. If you have a hard real-time requirement then a garbage-collected language may not be appropriate for you.
On Tue, Nov 27, 2012 at 5:19 AM, Jeff Shaw <[email protected]> wrote: > Hello, > I've run into an issue that makes me think that when the GHC GC runs while a > Snap or Warp HTTP server is serving connections, the GC prevents or delays > TCP connections from forming. My application requires that TCP connections > form within a few tens of milliseconds. I'm wondering if anyone else has run > into this issue, and if there are some GC flags that could help. I've tried > a few, such as -H and -c, and haven't found anything to help. I'm using GHC > 7.4.1. > > Thanks, > Jeff > > _______________________________________________ > Haskell-Cafe mailing list > [email protected] > http://www.haskell.org/mailman/listinfo/haskell-cafe -- Gregory Collins <[email protected]> _______________________________________________ Haskell-Cafe mailing list [email protected] http://www.haskell.org/mailman/listinfo/haskell-cafe
