One of my worst case scenarios completed in less then 21 minutes. Very
encouraging!!
Suppose I opened two connections each running 10 threads, would I approach 10
minutes? I'll give this a try later this week. This is pretty exciting for me
since I never seen this problem solved in less than
On Monday, 7 November 2016 19:54:35 UTC-5, Mandolyte wrote:
>
> Thanks for the quick response. and for your book - one of the best I've
> ever purchased!
>
Thanks! Glad it was helpful.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To
Thanks for the quick response. and for your book - one of the best I've
ever purchased!
To close the loop, optimal number of go routines is about 10 and the
database is actually Greenplum, a massively parallel processing
architecture based on an early fork of PG ... YMMV
On Monday, November
On Monday, 7 November 2016 16:57:29 UTC-5, Mandolyte wrote:
>
> I have what amounts to a recursion problem and I wrote a minimal test
> using go routines. I am able to vary the max number of go routines as a
> parameter on the command line (*). But the times don't vary much whether a
> single
