See this PR: https://github.com/apache/incubator-daffodil-site/pull/12
This is just one file of asciidoc.
You can access the file via checking out the branch:
git fetch asf refs/pull/12/head:pr/asf/12
git checkout pr/asf/12
I'm striving to create docs that can eventually be modified into arch
> By stream mode, do you mean using the JAVA API to not the CLI implementation?
> Meaning using Input/Output streams instead of command line interface?
The Daffodil CLI has a "--stream" flag you can use with parse and unparse.
When used in parse mode, Daffodil will first parse the input as norm
Steve,
On 2019/11/08 16:36:46, Steve Lawrence wrote:
> Hi Rob,
>
> I don't think you are subscribed to the dev list. I'd recommend you
> subscribe so you don't miss any responses if someone forgets to reply all.
>
> Before answering your questions, I'll reiterate that the -N option says
> how
Steve,
Thank you so much for the information! It is a huge help in understanding
the results!
I am going to perform similar tests using the JAVA API.
Rob
On 2019/11/08 16:36:46, Steve Lawrence wrote:
> Hi Rob,
>
> I don't think you are subscribed to the dev list. I'd recommend yo
Brandon,
Thank you so much for the useful information! It is a huge help!
I have a follow up question:
You mention " I would suggest either using daffodil in stream mode, or
using it as a library as part of a long-lived process "
By stream mode,
I'll point out that the times in the performance command do not include
JVM startup time or schema compilation time. Those numbers are purely
the parse time.
Though, we have seen some cases where using a pre-compiled schema can
make a difference so it's definitely worth a shot.
- Steve
On 11/8/1
Hi Rob,
I don't think you are subscribed to the dev list. I'd recommend you
subscribe so you don't miss any responses if someone forgets to reply all.
Before answering your questions, I'll reiterate that the -N option says
how many times to repeat the parse, the -t option says how many threads
to
I am not familiar with how daffodil's performance stats are reported
(particularly how the average rate is faster then the max rate).
However, the biggest bottlenecks for Daffodil performance is schema
compilation. If performance is a concern, I would recommend pre-compiling your
parser using t
All,
I am trying to port the Apache daffodil libraries onto an cross
domain guard that runs in a very small form factor.
We have cross compiled OpenJDK 12 for the aarch64 (ARM
processor) and loaded into memory.
I have built the source using sbt (s
