Aug 9, 2017 · 1 min read
Very nice article. Do you have any estimate for the total amount of resident memory of the process after all of the optimizations have been applied? Using the rough order-of-magnitude math above, the end result is 0B of excessive memory usage ((24GB+12GB+12GB+24GB)-48GB-24GB) but doesn’t indicate the average steady-state memory usage required to satisfy 3M connections. Approximate CPU efficiency for your workload with this setup would also be a nice number to see included. Again, fantastic article and thank you for highlighting some of the inherent concerns of scaling up a Go application.
