There are many factors that will determine how well your program performs. There are no guarantees that using more threads or goroutines is going to yield better performance. Sometimes throwing more threads or goroutines at a problem can slow things down. It really depends on the work you are doing and how you are doing it.
If you are just learning Go and concurrency start with solving a problem with one goroutine on a single thread. Then add more goroutines and threads slowly and measure the results. Is the performance gains you may get using two goroutines or more worth the complexity it required to get there? Was the program fast enough using one goroutine? What is most important to you for this particular problem, readability, simplicity or performance? There are lots of factors at play here. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
