Question: is that still a thing?

Asked By
jslovato
Asked At
2017-10-31 16:29:59

Found 15 possible answers.

User Answered At Possible Answer
lpar 2017-10-31 16:30:36 Yes. I know of software which calculates week numbers wrong in order to agree with Excel.
lbozza 2017-10-31 16:33:38 hey @xena It worked, thanks a bunch
xena 2017-10-31 16:33:44 yay glad to hear it worked
aslamsyed 2017-10-31 16:50:28 I have a http post end point and I need to put a load like 10000 request per second in golang Does any one have example?
imauld 2017-10-31 16:51:55 For how long?
zclark 2017-10-31 16:52:47 i like this tool for that https://github.com/tsenart/vegeta just cuz it's name and syntax mostly, but also its go
peterhellberg 2017-10-31 16:53:49 Or you can use wrk, or hey, or JMeter… Or a hosted service like loader.io or Apica
aslamsyed 2017-10-31 16:56:15 10000 requests Per second
jascott1 2017-10-31 16:56:32 locust ^ load testing https://locust.io/
imauld 2017-10-31 17:24:52 Yes 10k rps, but 10k rps for 1 second is a lot different than 10k rps for 10 minutes
rashton 2017-10-31 17:25:01 MFW I spend far too long trying to figure out json unmarshalling, and then immediately upon actually RTFM, I immediately figure it out :lul:
rackonnoiter 2017-10-31 18:11:20 Could anyone speak to the merits of explicitly passing a *sync.WaitGroup to a goroutine instead of just relying upon the closure's scope? The latter seems to tickle the race detector, but I'm not entirely sure why.
wkennedy 2017-10-31 18:31:16 This is more a philosophy answer then technical I think Are you replacing the pointer (write) at any given time? But sharing the WG with the function would not be a cause in and if itself for a data race. I like using closures because I think it help with reducing complexity and keeping the code clean. There are so many closure bugs that people trip up on, sometimes it may not be worth the mistakes
rackonnoiter 2017-10-31 19:06:42 @wkennedy , negative. Just calling wg.Done() from inside the anonymous goroutine was enough to trigger the race detector. *It was a defer wg.Done() to be specific. I haven't forgotten about emailing you either. Just busy, as per the norm.
wkennedy 2017-10-31 19:07:39 That should not be I don’t understand what it is finding. The race detector trace will show the goroutines at play and the read/write location So unless the wg variable itself is being replaced at some point The API is designed to be “Safe” I need to look at the code Hum

Related Questions