While working on the Stream performance issues, I noticed we have a performance hit on Windows for calls to the NewString API vs. what we had in 4.2. (Stream is implemented through the APIs, so NewString has quite an impact).
By building past revisions I traced it down to two commits, r11494 and r11503, which are both adding a significant amount of cycles to this API call, bringing total clock time up from some 1.5 usec to some 4.2 usec per call. See attached chart. Timings were done with Windows high-resolution timers, which occasionally show random spikes, but the overall picture seems to be consistent. Timings were done for both routine and method contexts. Both r11494 and r11503 are rather large commits, touching the dispatcher and other areas and it's not obvious for me what may be the cause. Are there any ideas what parts of these commits are introducing the increase? I didn't run the same tests on Linux, but I think this may be a Windows-only issue as NewString timings seem to be faster and unaffected by above commits, though as I said, I only have circumstantial evidence for this.
_______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
