Re: tcl versa python regarding performance

On 16.08.24 09:12, Christian Gollwitzer wrote:

Am 15.08.24 um 23:48 schrieb aotto1968:

a short conclusion from Facebook …
>
"If you analyze the C lib wrapper for MqReadI8, the TCL code adds about 200% wrapper load and the PYTHON code adds about 10% wrapper load." (ref: https://www.facebook.com/share/p/wihmQPR4pBRacLLF/)
>
→ I think TCL has an "performance-problem".

 I won't solve the problem, just to say: It's impossible to help you with this, because you don't explain:
* who wrote this wrapper
* where to find the code
* what benchmark are you running
 It could be, e.g. that your benchmark code introduces shimmering and then there's lots of conversion going on. It might be something completely different. Or it might be that Tcl is indeed slower than Python (in most of my comparisons, it was the opposite - unless you offload work to external libraries).
 Regards,
        Christian

1) just the "stupid" Tcl_ObjectGetMetadata to retrieve the pointer associated with an oo-object cost 1/3 of the wrapper performance → the whole header of a tcl OO wrapper cost more than everything else in the wrapper.
-> if you look into the code it is an hash-table lookup !!!
-> in python it is a ZERO-time operation
2) just to create an INT-object from an integer the TCL create always an object from scratch inclusive malloc etc
-> python uses for small numbers (integer) a table of already pre-alloc objects as ZERO-time operation
3) the set/reset-result have to free all the (stupid) objects that add additional 1/3 of the wrapper cost
analysis.
-> the Tcl_ObjectGetMetadata is clear an design-error
-> the missing small-int-object pre-alloc is an programmer-lazy-error
if someone can setup a screen sharing session than I can explain the problem in more detail
( need to test the screen-sharing first because because I not use to it )