Of that I’m not sure. It is based on deep knowledge of how these things are built from the hardware to the kernel to network protocols to the service layers. It broadly falls under performance tuning of which there is lots of literature. The key element of how channels and go routines play into this - is that when dealing with synchronous requests to a service (many services offer async endpoints) you need to be able to parallelize these. Then you need to be able to provide the data as fast as the network can accept it - most networks today are faster than disk storage - even some SSD. So then the disk storage array becomes the bottleneck and you need to parallelize that (RAID etc) and the kernel access. Often for massive uploads you might even partition the job across machines each with a portion of the data set. On May 11, 2025, at 11:04 AM, Kanak Bhatia <kanakbhati...@gmail.com> wrote: -- 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. To view this discussion visit https://groups.google.com/d/msgid/golang-nuts/01BE4694-0490-4FC9-A0BC-5EF366D9849A%40ix.netcom.com. |
- [go-nuts] Goroutines and channels optimization Kanak Bhatia
- [go-nuts] Re: Goroutines and channels optimizati... Jason E. Aten
- [go-nuts] Re: Goroutines and channels optimi... Jason E. Aten
- [go-nuts] Re: Goroutines and channels optimizati... ren...@ix.netcom.com
- Re: [go-nuts] Re: Goroutines and channels op... Kanak Bhatia
- Re: [go-nuts] Re: Goroutines and channel... Robert Engels
- Re: [go-nuts] Re: Goroutines and cha... Kanak Bhatia