I am experiencing some kind of a jamming effect with interpreted code.
If I am running the attached sample macro with 32 or less function calls, it takes my computer less than a second to run it through. With 33 calls, it takes 12 seconds.
Does cint have some internal buffer which is 32 instructions long? Can I increase it somehow?
Well, in my real world problem (filling histograms), most parameters are changing all the time, so a nested loop won’t do.
I am now compiling the code. Below jamming, this isn’t any faster than cint but it avoids the threshold. Actually, cint’s performance with bytecode generation is amazing!