Saxon » SaxonC

Here's a PHP snippet, it's quite simple:

    $saxonProcessor = new Saxon\SaxonProcessor();

    $catalog = getenv('XML_CATALOG_FILES');
    $saxonProcessor->setCatalog($catalog, true);

    $processor = $saxonProcessor->newXsltProcessor();
    $processor->setSourceFromFile($_FILES['xml']['tmp_name']);
    $processor->compileFromFile(__DIR__ . '/generated.xsl');
    $result = $processor->transformToString();

I haven't yet tried to reproduce this by running the PHP script on the command line, only as a web service in Apache.

hi,

I am having trouble running the transformation. The input.xml file seems to have dependencies. Such as the reference to JATS-archivearticle1.dtd. I will download this file too.

Apologies for not yet providing a complete repository for reproducing the issue - I can try to put one together in the next few days.

If you do want to try using the DTDs, you can download https://github.com/JATS4R/jats-dtds/archive/master.zip and point the catalog resolver to schema/catalog.xml in the unzipped archive.

Thanks. I have now got it to run.

Saxon on Java 9.9.1.4: 16 seconds

Saxon/C 1.1.2: PHP command-line takes 26 seconds.

Saxon/C 1.2.0 (pre-release): PHP on the command-line takes around 23 seconds.

Saxon/C 1.1 or 1.2 in the browser: Terminated maximum execution time 30 seconds for PHP exceeded.

Performance issues are sometimes difficult to get to the bottom of the cause. The memory should not blow up on Saxon/C as it does, maybe there are hotspots in the stylesheet which is causing the memory problem. I am investigating it further.

Update:

I managed to run the PHP script in the browser using a pre-release of Saxon/C on Excelsior JET 15.3 (MP1) enterprise which shows some improvements with the running time and memory. We are now turning our attentions to the profiling of the memory usage.