[Twisted-Python] combine local and remote calls in perspective brokers

2013-02-24 Thread Sergey Gerasimov 
Hello to all!

 

I'm using PB as communication protocol for components of my system.

Components can be located locally on the only one machine or in distributed
fashion. It depends on the config file.

 

At the moment all communications are implemented as callRemote calls. I
would like to keep this unified way of communication but make inter-machine
calls as efficient as possible. What is the best way to do that?

 

___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] Unable to write to "stuck" TCP client connections

2013-02-24 Thread Wenxiang Wu 
Hi,

I am encountering a weird bug, where some TCP client connections get into a
state where the server is able to read data sent from the client, but not
able to send any data with transport.write().

With some help from the #twitsed IRC channel, I was able to gather the
following information regarding the bug. While I'm still unable to provide
steps to reporduce this bug, I am able to reliably find clients who are in
this state. I am running 24 instances of the twisted server (Epoll reactor)
running on Ubuntu, with a peak traffic of >130k users. At any instance,
there are < 20 TCP connections stuck in this state.

Here is some information about the bug:

1. transport.write() does not send anything down the socket
2. transport.doWrite() will send all the data that has been buffered up,
and then stop sending any new data.
3. transport.writeSomeData() will send data
3. reactor.getWriters() will return a list of transports that are all stuck
in this state, and the writers will remain in this list.
4. Calling reactor.removeWriter(transport) will "unstuck" the transport and
data gets streamed once again.
5. A small number of clients will receive data for a while, and return to
this stuck state. Most return to normal once reactor.removeWriter() is
called.
6. Based on the suggestion from IRC user _habnabit, I used strace after
removing the writer, here is the output:

(4:52:09 PM) thewrongboy: epoll_ctl(3, EPOLL_CTL_MOD, 6504, {EPOLLIN,
{u32=6504, u64=22205092589476200}}) = 0
(4:52:09 PM) thewrongboy: epoll_ctl(3, EPOLL_CTL_MOD, 6504,
{EPOLLIN|EPOLLOUT, {u32=6504, u64=22205092589476200}}) = 0
 (4:52:09 PM) thewrongboy: epoll_ctl(3, EPOLL_CTL_MOD, 6504, {EPOLLIN,
{u32=6504, u64=22205092589476200}}) = 0
(4:52:09 PM) thewrongboy: epoll_ctl(3, EPOLL_CTL_MOD, 6504,
{EPOLLIN|EPOLLOUT, {u32=6504, u64=22205092589476200}}) = 0
 (4:52:09 PM) thewrongboy: epoll_ctl(3, EPOLL_CTL_MOD, 6504, {EPOLLIN,
{u32=6504, u64=22205092589476200}}) = 0

For now, I am using a LoopingCall to check and remove transports that are
stuck in getWriters().

I am using Twisted 12.3.0 on Ubuntu 12.04 - 3.2.0-35-generic #55-Ubuntu SMP
Wed Dec 5 17:42:16 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux.

Has anyone else experienced this weird problem? I'd love to provide more
information regarding this bug.
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] Unable to write to "stuck" TCP client connections

2013-02-24 Thread Itamar Turner-Trauring 
On Sun, Feb 24, 2013 at 7:22 PM, Wenxiang Wu  wrote:

> Hi,
>
> I am encountering a weird bug, where some TCP client connections get into
> a state where the server is able to read data sent from the client, but not
> able to send any data with transport.write().
>

Ignoring your workarounds, what transport methods do you use in normal
code? Obviously write(), but what else?
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] combine local and remote calls in perspective brokers

2013-02-24 Thread Itamar Turner-Trauring 
On Sun, Feb 24, 2013 at 11:23 AM, Sergey Gerasimov  wrote:

> Hello to all!
>
> ** **
>
> I’m using PB as communication protocol for components of my system.
>
> Components can be located locally on the only one machine or in
> distributed fashion. It depends on the config file.
>
> ** **
>
> At the moment all communications are implemented as callRemote calls. I
> would like to keep this unified way of communication but make inter-machine
> calls as efficient as possible. What is the best way to do that?
>

When you say "locally", is it still different processes talking to each
other? Talking over TCP loopback on the same machine is pretty efficient,
and unlikely to be a bottleneck, so you don't necessarily have to do
anything special.

-Itamar
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python