That is interesting because I was benchmarking it years ago it was only slower with programs that did a lot of external calls, and all programs with arithmetic were a lot faster than the interpreter. Anyway, all very good observations for new Rexx implementations. I share your observations about the Object Rexx implementation, of which the garbage collection always was the achilles heel. But did you test with the IBM implementation or the new 5.0.0 version? It seems to have become a lot faster over the years.
Is there a github repo with your benchmarks? Just because we are working on a new, VM and bytecode based Rexx system. René. > On 28 Feb 2023, at 13:49, David Crayford <dcrayf...@gmail.com> wrote: > > On 28/2/23 20:41, René Jansen wrote: >> Depending on what you test and what you want to see of course. You did use >> the Rexx compiler? > > Yes, and the REXX compiler was slower than the interpreter. I profiled it > using Application Performance Analyzer and it was spending 90% of it's time > in GETMAIN calls so it has sub-optimal memory management. The REXX compiler > should not be used if you are using medium to large stem variables or data > stacks. > > >> René. >> >>> On 28 Feb 2023, at 06:47, David Crayford <dcrayf...@gmail.com> wrote: >>> >>> On 25/2/23 01:23, Farley, Peter wrote: >>>> Python on the mainframe is pretty good, but still can't beat out Rexx in >>>> performance even when the Rex script needs to use BPXWUNIX and friends to >>>> access z/OS Unix file systems, >>>> >>> I have conducted a series of benchtests, and the results suggest that REXX >>> is not as fast as Python. In my testing, I compare the performance of C, >>> Lua, Python, and REXX, and the results are clear: C is the fastest, >>> followed by Lua, which is within an order of magnitude of C. Python comes >>> next, within an order of magnitude of Lua, and REXX consistently performs >>> the poorest. In addition to the performance factor, the vast Python >>> ecosystem compared to the limited options available for REXX also make it >>> an easy decision. Python is also simpler to extend with packages, while >>> REXX requires more effort and potentially complex steps, such as using >>> modern libraries that require Language Environment (LE). >>> >>> ---------------------------------------------------------------------- >>> For IBM-MAIN subscribe / signoff / archive access instructions, >>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to lists...@listserv.ua.edu <mailto:lists...@listserv.ua.edu> >> with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu <mailto:lists...@listserv.ua.edu> with > the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
