Best practice about mgo

[pjebs]

Can you please provide guidance (since you are the only authority on the matter) on how and when to use clone and copy.

[pjebs]

See also:
https://groups.google.com/forum/#!topic/mgo-users/pk9IsU2bb8o
http://stackoverflow.com/questions/33275357/should-i-copy-session-for-each-operation-in-mgo

[pjebs]

This is a copy of: https://github.com/go-mgo/mgo/issues/287 which the original author did not answer. Since the original author has now retired, I guess you are the highest power. It would be great if a higher power answered it because I noticed there are 100's of people asking the same question on forums and many are linking to my original issue.

Thank you for your time.

[pjebs]

Does this package do connection pooling similar to database/sql?

[domodwyer]

Hi @pjebs

You're not the first to ask this! I'd suggest using session.Copy() to automatically open a new socket to the Mongo server if needed, or reuse an existing socket if available. This means your application will "warm up" to the number of connections needed for the load in the first few minutes of operation.

You could use Clone() which uses the same underlying socket, but past a certain level of concurrency your application will be bound by contention caused by sharing the single socket. Depending on your workload this might not be an issue, but it's likely going to be a nasty surprise!

Calling Dial each time involves opening a connection, performing any authentication (not cheap) and then closing it when you're done, having to do it all again for the next request - this is a lot of round trips and very expensive for both the client and server - you should avoid this method.

I've added an example to the documentation - this should make it into the master branch / godoc.org soon.

I hope this helps, does it answer all your questions?

Dom

[pjebs]

thank you.