bia@programming.devOPtoGolang@programming.dev•Comparing memory usage between node.js object and go map[string]interface{}
1·
29 days agoheap dump from pprof
heap dump from pprof
Maybe I’m wrong, but using http could create a MITM vulnerability.
And for me this issue is my browser is setup to block http URLs. It’s just not a good look.
Hmmm, hosting a hacker post without an https url… 🤨
I’m looking at the memory reported by metrics-server in EKS, as that what I base the container resource scaling on. Maybe the go process is reporting memory in a way that doesn’t represent the “actual” usage. But I’m not sure it matters here, unless I can get it to change the reported memory usage.
Please see the heap dump I added for 10000 devices. Reported memory is 1,1 GB.