Tornado: FriendFeed's non-blocking Python web server is now open source

Re:Tornado: FriendFeed's non-blocking Python web server is n... by eggnet on Friday September 11, 2009 @03:32AM (#817005)

I believe this is one of the advantages of 64 bit architectures. That meg of stack size is just a reservation, it's not actually used, unless your thread really needs it. On a 64 bit machine there is plenty of space to allocate.

[ Parent | on HN ]

Re:Tornado: FriendFeed's non-blocking Python web server is n... by agazso on Friday September 11, 2009 @06:22AM (#817111)

Yeah, but why would you waste it for stack space, when you can do an event-driven design, and allocate the resources only when needed?

Anyways, I was talking about C, where the stack is allocated when the thread is created and you cannot resize it later, nor it will grow automatically.

With dynamic languages it is different, but don't expect handling that much connections with them either.

[ Parent | on HN ]

Re:Tornado: FriendFeed's non-blocking Python web server is n... by riobard on Friday September 11, 2009 @11:09AM (#817466)

It doesn't solve the context _switching_ cost.

[ Parent | on HN ]

Re:Tornado: FriendFeed's non-blocking Python web server is n... by kingkongrevenge on Friday September 11, 2009 @11:42AM (#817528)

This just isn't a substantial cost any more. With the latest kernels, thread per connection servers are competitive with event driven servers. This was not true a few years ago.

[ Parent | on HN ]