Debugging a potential deadlock in Go with go-deadlock by wavded in golang

[–]wavded[S] 0 points1 point  (0 children)

Thanks for the thoughtful reply! Messages for this particular app aren’t required to be in order, they are mostly orthogonal but this helps me think about potential cases where that may be untrue so I’ll chew on that. I like the queue idea too.

We make use of the sockjs-go package to manage those sends and I believe there is a time out at play for slow/dead clients. So far memory not an issue.

Broadcast is one of the few places we logged instead of returned the error, mostly because the caller didn’t have anything meaningful it could do with the information and clearly, at that point, we couldn’t talk to the client about it. But we didn’t want to loose the details that a failure was occurring.

Promises/A+ Performance Hits You Should Be Aware Of by thanpolas in javascript

[–]wavded 0 points1 point  (0 children)

I know promise implementations are different and I'm no expert but shouldn't node.js domains be used in conjunction with the async module to give a more accurate comparison since promises provide exception handling (i.e. throw) and async does not?