Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> for something like long polling or web sockets

Are you imagine this scenario or you are actually using Flask for long polling? What's your Flask websocket setup looks like?

FYI Flask internal does not stop you from using thousands of threads of greenlets to process concurrency. And web request-response model is embarrassingly parallel on multi-core. Just spawn one worker per core.

For a simple API service if you can not handle 3K rps per Flask instance you are doing it wrong.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: