I've to starting to play with Go to manage the concurrency and it's awesome.
On 16 dic, 23:51, Damjan <gdam...@gmail.com> wrote: > > One other issue is that the thread overhead is not usually the > > bottleneck in a WSGI application. Database access has a much bigger > > impact on performance. If you need to handle thousands of > > simultaneous requests, you probably need multiple servers anyway. > > depends, > if you need to handle thousands of requests that are at the same time > pretty idle (see Comet for ex), the memory that threads consume is a > big issue. > > An event based framework solves this by saving as litle state as > needed (or possible) so that it could handle a large number of > otherwise slow or idle connections. > > Python in general is not so well suited for all of this. I've been > playing with Erlang latelly and this kind of stuff is impresivelly > easier there. -- You received this message because you are subscribed to the Google Groups "pylons-devel" group. To post to this group, send email to pylons-de...@googlegroups.com. To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en.
