data file is a point of uncertainty.
> >>
> >> On Tue, Jan 9, 2024 at 1:49 PM Larry Barber
> >> wrote:
> >>
> >>> Seems like the benefit would only be significant if you were dealing
> >>> with
> >>> lots of variables.
> >
of variables.
-Original Message-
From: Mike Beckerle
Sent: Tuesday, January 9, 2024 1:39 PM
To: dev@daffodil.apache.org
Subject: Thoughts on on demand copying of parser state
Right now we copy the state of the parser as every point of
uncertainty is
reached.
I am speculating that we could
: Mike Beckerle
Sent: Tuesday, January 9, 2024 1:39 PM
To: dev@daffodil.apache.org
Subject: Thoughts on on demand copying of parser state
Right now we copy the state of the parser as every point of uncertainty is
reached.
I am speculating that we could copy on demand. So, for example
Original Message-
> From: Mike Beckerle
> Sent: Tuesday, January 9, 2024 1:39 PM
> To: dev@daffodil.apache.org
> Subject: Thoughts on on demand copying of parser state
>
> Right now we copy the state of the parser as every point of uncertainty is
> reached.
>
&
It's definitely worth considering.
DAFFODIL-2852 showed that variable copies can definitely have lot of
overhead. Though the commit to resolve that issue reduced it pretty
substantially, and I believe that change made variable copies disappear
from profiling (but I'm not positive).
In my
Seems like the benefit would only be significant if you were dealing with lots
of variables.
-Original Message-
From: Mike Beckerle
Sent: Tuesday, January 9, 2024 1:39 PM
To: dev@daffodil.apache.org
Subject: Thoughts on on demand copying of parser state
Right now we copy the state
Right now we copy the state of the parser as every point of uncertainty is
reached.
I am speculating that we could copy on demand. So, for example, if no
variable modifying operation occurs then there would be no overhead to
copy the variable state.
This comes at the cost of each variable doing
