vit...@synapticvision.com пишет:
> Sorry, forgot to mention, per second.
> Amount of concurrent connections per second.
Just for example, in my tests standard twisted http server can do about 1k
dummy
req/resp per second on one modern cpu core.
>
> Quoting "Eero Nevalainen" :
>
>> vit...@syna
vit...@synapticvision.com пишет:
> hi,
> what would be expected amount(+-) of concurrent connections
Why this should depend on size of responses/requests?
for
> twisted reactor if single request to gateway eq 1Kb and response back
> 30Kb (I mean response data much more bigger than request)? (
Laurens Van Houtven пишет:
> Are you sure it's dying out because of CPU limitations?
Yes, with 1k req/s cpu is 100% busy with python.
> Can you show any real applications where this happens?
I do not have real application in python/twisted now.
That could be any internet server with high load
Glyph Lefkowitz пишет:
> On Fri, Sep 4, 2009 at 4:59 PM, Bokhan Artem <mailto:a...@academ.org>> wrote:
>
> Hello.
>
> Is there right (standard) way to write twisted network server
> (tcp/web/mail/etc) which could use several cpu cores? For example,
>
Hello.
Is there right (standard) way to write twisted network server
(tcp/web/mail/etc) which could use several cpu cores? For example,
master+workers model, where every worker doing the same job.
If so, may somebody help to wrap the sample code below?
May be some well-known twisted based software
