Hi, Johann
Few words about load script: each "client" is a thread, which wait
from 7 to 15 seconds and then make request to nginx, nginx proxy
requests to api-server. On every request api-server makes 3 callRemote
to memory-db. Delay between creating clients - 0.1 sec.
Currently I use 1 amp-conne
Vlad Shevchenko wrote:
> Thanks a lot, Stephen.
>
> AMP probably is what I looking for. Now I can handle a much more
> clients (2 times more without significantly increasing response time).
> Server can also handle 3 times more clients without any errors, but
> response time grow up. I check for ne
Thanks a lot, Stephen.
AMP probably is what I looking for. Now I can handle a much more
clients (2 times more without significantly increasing response time).
Server can also handle 3 times more clients without any errors, but
response time grow up. I check for netstat and find out Recv-Q about
17
Vlad Shevchenko wrote:
> I have developed two kind of servers:
>api - http server
>memory_db - dict-based server with some logic of putting data to dict
> and getting it back.
Sounds a bit like tuple spaces.
--
Eero
___
Twisted-Python mailing
Vlad,
Have you considered using twisted.protocols.amp ?
--
Regards,
Stephen Thorne
Development Engineer
Netbox Blue
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
here is some statistic:
low network traffic
===
Json-RPC PB
average MIN 0.016 average MIN 0.011
average MAX 0.044 average MAX 0.029
AVG 0.027 AVG 0.017
90% line 0.02790% line 0.017
CLIENTS 139
Really I need a large amount of data to be available before I can
begin calculations, Json-PRC vs. PB provide a 10+ times smaller
response time for same returning data
On Tue, Feb 16, 2010 at 10:08 PM, Phil Christensen wrote:
> On Feb 16, 2010, at 2:46 PM, Vlad Shevchenko wrote:
> > I have devel
On Feb 16, 2010, at 2:46 PM, Vlad Shevchenko wrote:
> I have developed two kind of servers:
>api - http server
>memory_db - dict-based server with some logic of putting data to dict and
> getting it back.
>
> Api communicate with memory_db via txJSON-RPC but response time is huge under
>
Hi,
I have developed two kind of servers:
api - http server
memory_db - dict-based server with some logic of putting data to dict and
getting it back.
Api communicate with memory_db via txJSON-RPC but response time is huge
under high load. I also try implementation with replacement txJSON-R
