>
> What cgo calls were those? Are you using an alternative crypto
> implentation?
Sadly, I didn't save any of the metrics I gathered any more, so I can't say
specifically what CGO calls were being used by my application. I do recall
a good bit of the memory being spent on checking the certificat
Problem resolved. Application was allocating a new http.Client for every
remote call made, and since the handshake ultimately comes down to CGO
calls, I was accumulating memory that was not managed by Go's GC.
On Tuesday, March 14, 2017 at 8:21:58 PM UTC-4, Nathan Morley wrote:
>
Hello,
So I've written a small service in my free time that essentially pulls data
from a RESTful API at a high rate, and store it in a database. While there
is no rate limiting in place and I'm free to hit it as hard as I like with
as many connections I need, I only have 5 workers going at a t
Hey all,
I have a brief question on the "best practices" for documenting Go code. I
did a quick sweep through the official blog as well as the Effective Go
article, but found no answer as of yet...
Let's say I have an interface like a database driver that gets implemented
in multiple places. W
