go is perfectly fine with such amount of goroutines. Of course you should be aware of memory consumption, probably few hundred of megabytes (each goroutiine need at least 2kB). I think you should focus on avoiding to many goroutines at the same time (this could slow down your webserver) and limiting concurrently fetched feeds. Probably you should also increase file descriptiors for your app and adjust keep alive timeout for feed's http connections. Every connection uses one file description, doesn't matter if it's connection from your app or to your app.
W dniu piątek, 4 listopada 2016 22:14:24 UTC+1 użytkownik Marwan abdel moneim napisał: > > i am building a web site that includes a rss aggregator > now, the idea i have is making a goroutine for every rss feed that should > learn by time when to update the feed > these goroutines sleeps for a while then send job to some channel then go > to sleep again > > so there could be a thousands of goroutines sleeps at the same time, is > this efficient? or it would have a huge impact on performance? > > is this a bad way for implementing rss aggregator? > -- 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.
