__
From: Rose, Rob P
Sent: Friday, November 8, 2019 12:41 PM
To: dev@daffodil.apache.org
Cc: Hanna, Maria
Subject: RE: CLI Performance usage...
Brandon,
Thank you so much for the useful information! It is a huge help!
I have a follow up question:
You mention &quo
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
rser, parse the data according to the schema,
and output the data to the console or file?
Thanks so much again!
Rob
-Original Message-
From: Sloane, Brandon
Sent: Friday, November 8, 2019 11:35 AM
To: dev@daffodil.apache.org
Cc: Hanna, Maria
Subject: Re: CLI Performance usage...
I am n
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
