3 ms·
(Cockroach Labs co-founder) I gave a talk on exactly this subject at the ACM Applicative conference last year: https://www.cockroachlabs.com/community/tech-talk
by bdarnell 9y ago
(Cockroach Labs co-founder) I gave a talk on exactly this subject at the ACM Applicative conference last year: https://www.cockroachlabs.com/community/tech-talks/challenges-writing-massive-complex-go-application/ https://www.cockroachlabs.com/community/tech-talks/challenge...
Overall we've been happy with the choice. The GC is sometimes a performance issue, but it's manageable (and Go gives you better tools to limit the cost of GC than many other garbage-collected languages)
- rjammala 9y agoThanks for the video. Can you please upload the slides somewhere?
- arjunnarayan 9y agoWe were told that the slides would be uploaded by Applicative (hence we didn't post a copy), but we can't seem to find it on the internet either, so here's a copy from our Google drive: https://drive.google.com/file/d/0ByQnrkOiRT_LMmZ6SXFmbk5wTDA/view?usp=sharing https://drive.google.com/file/d/0ByQnrkOiRT_LMmZ6SXFmbk5wTDA...
- rjammala 9y agoThanks! Arjun.
- fortytw2 9y agoDid y'all ever figure out a way to get goroutine leak detection working with parallel tests? (didn't expect to see that linked here)
- bdarnell 9y agoWe have started parallelizing our tests with the new subtest feature: leaktest in the top-level test, t.Parallel in the subtests. This means we only check for leaks in between batches of parallel subtests. This works OK for us for now since our slowest "test" is really a huge data-driven test suite, and that's the only place we're currently parallelizing, although it would be better if we could parallelize more of our tests.