I'll look at this again monday, but I was watching progress using
VisualVM, and the GC overhead is minimal (under 10%).
The system was definitely not thrashing. There was some free memory.
Note also that the output files from the compilation are still
small-ish (8MBytes).
One curious thing was
I remember testing that schema with 3.7.0 and it did not take that long to
compile, and I don't think there have been any real changes to compilation in 3.8.0.
Maybe this is a memory issue? daffodilPackageBin forks a process for compilation
so if that process doesn't have enough memory it
-1 binding
[OK] Verified all signatures, md5, sha1, sha512, etc. Log of that is
at the bottom of this message:
[OK] Regression tested 79 DFDL schemas that Owl has in a repository.
All that are expected to pass, either passed immediately, or passed
once the schemas were adapted for the new
layers
Lola,
I retested the URLs you mention and both work fine for me.
However, the s.apache.org/daffodil-issues-3.8.0 page requires you to
be logged in to JIRA to see the issues list, so I changed it to be a
link to an equivalent jira query that does not require login.
I have no idea what the
