Golang Http Client and Compression
I had a very (seemingly) simple task. Verify my golang http client, talking with an ElasticSearch cluster, is compressing data on wire. Because in trials, there was around 8x data compression and 100ms latency improvement. Sounds simple? Apparently not! ElasticSearch Side of Things Http compression is enabled by default and it’s an easy configuration. Despite it being enabled by default, still added following in config http.compression: true And verified it works by...