If Tcl_Obj references were sent via sys_vgui instead of Tcl code, I think you could reduce the network traffic down to like 10% of what it is now. Plus, using Tcl_Obj, each chunk of Tcl code would only be compiled once per run (the bytecode is stored as part of the Tcl_Obj). It's not going to change the world, but I think it would be noticeable.
.hc
On Mar 6, 2008, at 5:51 PM, Miller Puckette wrote:
I rather doubt this can relly help given the way Pd uses Tcl/Tk. (I still have a pet idea on the other hand of simply parsing the TCL code and passing it to GTK :)
cheers M
On Thu, Mar 06, 2008 at 05:26:00PM -0500, Hans-Christoph Steiner wrote:
Now that I have discovered this bytecode caching feature, I am curious if the changes I made have made any performance differences. Also, matju mentioned that the bytecode caching probably works better if reusing procs, so it could make sense to have sys_vgui calls use Tcl procs, so that the bytecode gets reused.
I was also thinking that perhaps sys_vgui communications could use Tcl_Obj references instead of sending whole lines of Tcl, but that might get overly complicated.
.hc
http://at.or.at/hans/
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
------------------------------------------------------------------------ ----
The arc of history bends towards justice. - Dr. Martin Luther King, Jr.