[go-nuts] Re: Server RAM size as a function of the number of goroutines???

If I understood your scenario correctly, I would assume that it is not the Goroutines overhead per se but the traceroute command processes spawned in the Goroutines that drives the resource demand. The pure Goroutine memory overhead should be quite neglectable (size of G struct + initial dynamic

[go-nuts] [ANN] End-to-end request monitoring for Go applications: No code changes required

Dynatrace blog article elaborates on recent Go technology monitoring enhancements. Request monitoring without manual instrumentation / source code changes. -- You received this me

[go-nuts] Re: What will happen if the go and cgo's malloc return overlapped ?

C/C++ runtime library allocations and Go memory allocation do not "overlap". C/C++ runtime and Go heap will reserve memory pages on which they operate from the operating system. This will ensure, that both memory management systems will use non overlapping memory areas. Am Freitag, 22. Septem

[go-nuts] [ANN] Dynatrace announced support for Go applications

First auto-instrumenting monitoring solution available for Go-based applications. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsub

[go-nuts] Re: Best way to launch/monitor several go process in production

For the monitoring part I can recommend https://www.dynatrace.com/technologies/golang-monitoring (https://www.dynatrace.com/blog/introducing-fully-automated-support-for-go-based-application-monitoring/). Am Sonntag, 3. September 2017 23:35:30 UTC+2 schrieb emarti...@gmail.com: > > Hello, > > I a