Strangely we just tried deploying a really simple one but with large-ish POST payloads. For some reason the number of requests/s would never match what would hit the nginx servers directly without the Go proxy.
wrk & ab profiles were able to cope but as soon as any real world traffic hit the server we saw issues. This was our latest attempt... https://gist.github.com/leearmstrong/b5e09b76df484fbdf1f7a47883d38c83 On Tuesday, March 21, 2017 at 10:55:55 PM UTC, James Pettyjohn wrote: > > I'm looking at using the stock HTTP reverse proxy, briefly looking at the > implementation it seems to be ready to withstand a production workload. > > Any cautions or caveats in going this route? > > - J > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
