Time |
S |
Nick |
Message |
03:29 |
|
pdurbin |
activity 1 posted: http://www.becomingadatascientist.com/learningclub/thread-55.html |
22:04 |
|
pdurbin |
ruby version: 94 seconds. regular go version: 2.8 seconds. goroutine version: 1.4 seconds |
22:05 |
|
pdurbin |
the example at https://golang.org/pkg/sync/#WaitGroup was helpful. I'm still getting used to goroutines. was looking at http://stackoverflow.com/questions/9543835/how-best-do-i-keep-a-long-running-go-program-running |
22:07 |
|
pdurbin |
WaitGroup makes a lot more sense to me that preventing main() from exiting by requiring keyboard input: https://gobyexample.com/goroutines |
22:12 |
|
pdurbin |
of course, this is on my laptop which has 4 processors. the goroutine version is no faster on my digital ocean vm that only has 1 cpu |
22:13 |
|
pdurbin |
there's a certain irony in the fact that I'm learning go partially because I'm interested in its concurrency primitives yet "in production" (on my little VM) I can't take advantage of them because I only pay for one cpu :) |
22:13 |
|
pdurbin |
for 5 bucks a month I'm not complaining :) |