[jboss-jira] [JBoss JIRA] (DROOLS-4735) [DMN Designer] Grid performance is dire
Michael Anstis (Jira)
issues at jboss.org
Tue Nov 19 05:03:00 EST 2019
[ https://issues.jboss.org/browse/DROOLS-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Anstis updated DROOLS-4735:
-----------------------------------
Description:
There have been reports that the performance of the DMN editor's grids does not scale. On examination performance for anything other than simple examples is pretty dire.. something is seriously wrong.
On closer inspection the following issues were found:
- Multiple {{NodeMouseDownHandler}}, {{NodeMouseMoveHandler}} and {{NodeMouseUpHandler}} are registered because multiple {{DMNGridLayer}} are (incorrectly) instantiated due to a flaw in {{GridLienzoPanel}} and {{GridLienzoScrollHandler}}.
- Calls to {{GridWidget.getHeight()}} and {{GridRow.getHeight()}} can be _very_ expensive for due to the dynamic calculation in {{ExpressionEditorGridRow}} and {{LiteralExpressionGridRow}} rows.
h2. Manual Acceptance test
h3. GDT
- Merge view
- Pinned mode
- Change column width, save and reopen
- Search the table
- Scroll the table
- Edit the cell
- Reorder columns
- Reorder rows(? not sure this is possible with GDT)
h3. DMN
- Context ( Context (Decision Table, Relation, Invocation))
- Change column width, save and reopen
- Search the grid
- Scroll the grid
- Reorder columns
- Reorder rows
was:
There have been reports that the performance of the DMN editor's grids does not scale. On examination performance for anything other than simple examples is pretty dire.. something is seriously wrong.
On closer inspection the following issues were found:
- Multiple {{NodeMouseDownHandler}}, {{NodeMouseMoveHandler}} and {{NodeMouseUpHandler}} are registered because multiple {{DMNGridLayer}} are (incorrectly) instantiated due to a flaw in {{GridLienzoPanel}} and {{GridLienzoScrollHandler}}.
- Calls to {{GridWidget.getHeight()}} and {{GridRow.getHeight()}} can be _very_ expensive for due to the dynamic calculation in {{ExpressionEditorGridRow}} and {{LiteralExpressionGridRow}} rows.
h2. Manual Acceptance test
h3. GDT
- Merge view
- Pinned mode
- Change column width, save and reopen
- Search the table
- Scroll the table
- Edit the cell
- Reorder columns
h3. DMN
- Context ( Context (Decision Table, Relation, Invocation))
- Change column width, save and reopen
- Search the grid
- Scroll the grid
- Reorder columns
> [DMN Designer] Grid performance is dire
> ---------------------------------------
>
> Key: DROOLS-4735
> URL: https://issues.jboss.org/browse/DROOLS-4735
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.29.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Critical
> Labels: drools-tools
>
> There have been reports that the performance of the DMN editor's grids does not scale. On examination performance for anything other than simple examples is pretty dire.. something is seriously wrong.
> On closer inspection the following issues were found:
> - Multiple {{NodeMouseDownHandler}}, {{NodeMouseMoveHandler}} and {{NodeMouseUpHandler}} are registered because multiple {{DMNGridLayer}} are (incorrectly) instantiated due to a flaw in {{GridLienzoPanel}} and {{GridLienzoScrollHandler}}.
> - Calls to {{GridWidget.getHeight()}} and {{GridRow.getHeight()}} can be _very_ expensive for due to the dynamic calculation in {{ExpressionEditorGridRow}} and {{LiteralExpressionGridRow}} rows.
> h2. Manual Acceptance test
> h3. GDT
> - Merge view
> - Pinned mode
> - Change column width, save and reopen
> - Search the table
> - Scroll the table
> - Edit the cell
> - Reorder columns
> - Reorder rows(? not sure this is possible with GDT)
> h3. DMN
> - Context ( Context (Decision Table, Relation, Invocation))
> - Change column width, save and reopen
> - Search the grid
> - Scroll the grid
> - Reorder columns
> - Reorder rows
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
More information about the jboss-jira
mailing list