You should read the comments following the article you referenced. In addition there is a long thread on hackernews that might be worth browsing: https://news.ycombinator.com/item?id=36024209
But if you want a real insight into how concurrent programs behave, you are better off writing your own toy benchmarking programs that focus on various aspects of concurrency. Then you can modify them to measure such metrics for your specific applications. > On Jun 6, 2023, at 7:58 PM, Nikhilesh Susarla <nikhilesh1...@gmail.com> wrote: > > I was going through a blog where they compare different language threads to > see how much memory they consume for a million tasks. > > Blog : https://pkolaczk.github.io/memory-consumption-of-async/ > > Do we have any benchmarking/report before that Go routines take more memory > with more threads? > > I know we can't consider it to be ideal but any reasons that the memory > spiked up? > Is there any blog to read more about go routines and their memory > consumptions? > > Thank you > > -- > 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 > <mailto:golang-nuts+unsubscr...@googlegroups.com>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/golang-nuts/0af076cc-8b5d-491b-88f5-599dbd37c056n%40googlegroups.com > > <https://groups.google.com/d/msgid/golang-nuts/0af076cc-8b5d-491b-88f5-599dbd37c056n%40googlegroups.com?utm_medium=email&utm_source=footer>. -- 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 on the web visit https://groups.google.com/d/msgid/golang-nuts/DC4AD442-587D-4070-8B5D-503466F00A7B%40iitbombay.org.
