On Fri, Oct 27, 2023 at 11:57:12AM +0100, Gavin Smith wrote: > > I wasn't talking about whether they would work or not, I was talking about > how fast they would run.
Ok. > At the moment, performance improvements from the new code seem hypothetical. Actually, my guess was that there would also be a performance improvement with the XS overrides of parser post-processing/Structuring/Transformations, but very small or unnoticeable. The fact that there is some worsening is actually a bit mysterious to me -- except if it is explained by the rebuild of the tree, as one should normally easily be avoided as said in another mail. I can work on that later, but I would like to finish at least partly the HTML XS converter before. The code is very new, too, so bugs are not out of the question, including big ones. > For example, in the Info/plaintext output, it is slower than before, > presumably to new processing that didn't take place before. In this case, > there is the XS parser, other XS processing, and then a plain Perl converter > with a few XS functions. This is not "everything is done in XS", but a > case that is worth being concerned about. > > It seems like it should be possible with a bit of tweaking to avoid this > slowdown without rewriting the whole Plaintext converter in C. I think so too. -- Pat
