You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@daffodil.apache.org by "Dave Thompson (Jira)" <ji...@apache.org> on 2021/11/01 20:50:00 UTC

[jira] [Closed] (DAFFODIL-2572) Regression in schema compilation memory requirements

     [ https://issues.apache.org/jira/browse/DAFFODIL-2572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dave Thompson closed DAFFODIL-2572.
-----------------------------------

Verified the specified commit (commit 5dea1caffebd89b91b538218dc751c7b62c63773) is included in the latest pull from the daffodil repository.

Verified changes identified in commit comment were implemented.

Verified all affected daffodil subproject sbt test suites execute successfully.

Aquired suspect schema link16-mda repo from Steve L.

Rolled commit back to prior to fix commit and reduced DAFFODIL_JAVA_OPTS to 1GB to force compile fail for out of memory.

Checked out fix commit, rebuild daffodil and verified the schema now compile with DAFFODIL_JAVA_OPTS at 1GB.

 

> Regression in schema compilation memory requirements
> ----------------------------------------------------
>
>                 Key: DAFFODIL-2572
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-2572
>             Project: Daffodil
>          Issue Type: Bug
>          Components: Performance
>            Reporter: Steve Lawrence
>            Assignee: Steve Lawrence
>            Priority: Major
>             Fix For: 3.2.0
>
>
> I have a fairly large schema that compiles successfully on 3.1.0 with 200MB of memory given to the JVM.
> With the current main branch, I have to bump the memory up to 1300MB before it compiles, otherwise I get an OutOfMemoryException. This is about a 7x bump in memory.
> Git bisect pinpointed the regression to commit 62ac1047a18979bea1f5d6c668eefeaaae39d64b
> Skimming that commit, nothing immediately jumps out at me as a significant change to what we already did, so I'm not sure exactly what caused this regression.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)