On Wed, 31 Oct 2007, Hans-Christoph Steiner wrote:
This is not where the bottleneck is.
I thought the network socket was the bottleneck. The example I am thinking
of is getting the mouse pointer coords from Tk. That generates a lot of
network traffic, it would be nice this happened in the pd process instead.
Obviously, using the C interface to draw to the screen wouldn't be useful.
What I wrote to Carmen is because I think that the network socket is not
the bottleneck, so I told what I think the problem is about the network
socket.
The bottleneck is most of all the Tk rendering itself.
Something that may make one think that the bottleneck is in the network
socket, is that when the Tk rendering takes too much time, it saturates
the pipe, which causes (or caused) pd to pause waiting for the Tcl/Tk
process to be less busy.
I think that since 0.38 or so, if the Tcl/Tk process is continually too
busy, Pd grows the output socket queue until Pd blows up by out-of-memory.
_ _ __ ___ _____ ________ _____________ _____________________ ...
| Mathieu Bouchard - tél:+1.514.383.3801, Montréal QC Canada
_______________________________________________
[email protected] mailing list
UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
