[JBoss JIRA] (DROOLS-4735) [DMN Designer] Grid performance is dire
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4735?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4735:
--------------------------------
Attachment: cell-edit-mode.webm
> [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
> Attachments: aTable.dmn, add-new-column.webm, cell-edit-mode.webm, delete-column.webm, drag-scroll.webm, dtable-500-rows.dmn, reorder-columns.webm, resize-column.webm, resized-column-save.webm, search-trough-grid.webm
>
>
> 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
> Environment: wildfly14 with following memory settings: {{JAVA_OPTS="-Xms64m -Xmx1024m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=1024m -Djava.net.preferIPv4Stack=true"}}
> 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 (/)
> h3. DMN decision table
> - Change column width, save and reopen (x) [^resize-column.webm] [^resized-column-save.webm]
> - Search the grid (/) [^search-trough-grid.webm]
> - Scroll the grid (?) scrolling seems working in reasonable time assuming number of rows, however dragging canvas is slower [^drag-scroll.webm]
> - Reorder columns (x) was not able to do it, still header popups shown [^reorder-columns.webm]
> - Reorder rows
> - Adding column (?) adding column is reasonable time assuming table size, however displaying and hiding context menu is quite slow [^add-new-column.webm]
> - Removing column (/) fine, acceptable ignoring time of showing menu reported above [^delete-column.webm]
> - Edit the cell (x) invoking the edit mode by double click is very slow, by keyboard it is fine
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (DROOLS-4735) [DMN Designer] Grid performance is dire
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4735?page=com.atlassian.jira.plugi... ]
Jozef Marko 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
Environment: wildfly14 with following memory settings: {{JAVA_OPTS="-Xms64m -Xmx1024m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=1024m -Djava.net.preferIPv4Stack=true"}}
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 (/)
h3. DMN decision table
- Change column width, save and reopen (x) [^resize-column.webm] [^resized-column-save.webm]
- Search the grid (/) [^search-trough-grid.webm]
- Scroll the grid (?) scrolling seems working in reasonable time assuming number of rows, however dragging canvas is slower [^drag-scroll.webm]
- Reorder columns (x) was not able to do it, still header popups shown [^reorder-columns.webm]
- Reorder rows
- Adding column (?) adding column is reasonable time assuming table size, however displaying and hiding context menu is quite slow [^add-new-column.webm]
- Removing column (/) fine, acceptable ignoring time of showing menu reported above [^delete-column.webm]
- Edit the cell (x) invoking the edit mode by double click is very slow, by keyboard it is fine [^cell-edit-mode.webm]
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
Environment: wildfly14 with following memory settings: {{JAVA_OPTS="-Xms64m -Xmx1024m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=1024m -Djava.net.preferIPv4Stack=true"}}
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 (/)
h3. DMN decision table
- Change column width, save and reopen (x) [^resize-column.webm] [^resized-column-save.webm]
- Search the grid (/) [^search-trough-grid.webm]
- Scroll the grid (?) scrolling seems working in reasonable time assuming number of rows, however dragging canvas is slower [^drag-scroll.webm]
- Reorder columns (x) was not able to do it, still header popups shown [^reorder-columns.webm]
- Reorder rows
- Adding column (?) adding column is reasonable time assuming table size, however displaying and hiding context menu is quite slow [^add-new-column.webm]
- Removing column (/) fine, acceptable ignoring time of showing menu reported above [^delete-column.webm]
- Edit the cell (x) invoking the edit mode by double click is very slow, by keyboard it is fine
> [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
> Attachments: aTable.dmn, add-new-column.webm, cell-edit-mode.webm, delete-column.webm, drag-scroll.webm, dtable-500-rows.dmn, reorder-columns.webm, resize-column.webm, resized-column-save.webm, search-trough-grid.webm
>
>
> 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
> Environment: wildfly14 with following memory settings: {{JAVA_OPTS="-Xms64m -Xmx1024m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=1024m -Djava.net.preferIPv4Stack=true"}}
> 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 (/)
> h3. DMN decision table
> - Change column width, save and reopen (x) [^resize-column.webm] [^resized-column-save.webm]
> - Search the grid (/) [^search-trough-grid.webm]
> - Scroll the grid (?) scrolling seems working in reasonable time assuming number of rows, however dragging canvas is slower [^drag-scroll.webm]
> - Reorder columns (x) was not able to do it, still header popups shown [^reorder-columns.webm]
> - Reorder rows
> - Adding column (?) adding column is reasonable time assuming table size, however displaying and hiding context menu is quite slow [^add-new-column.webm]
> - Removing column (/) fine, acceptable ignoring time of showing menu reported above [^delete-column.webm]
> - Edit the cell (x) invoking the edit mode by double click is very slow, by keyboard it is fine [^cell-edit-mode.webm]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (WFWIP-269) Headers should not be added if header name contains a colon
by Tomas Terem (Jira)
[ https://issues.jboss.org/browse/WFWIP-269?page=com.atlassian.jira.plugin.... ]
Tomas Terem commented on WFWIP-269:
-----------------------------------
[~dlofthouse] I though about this more and I updated issue name and description.
> Headers should not be added if header name contains a colon
> -----------------------------------------------------------
>
> Key: WFWIP-269
> URL: https://issues.jboss.org/browse/WFWIP-269
> Project: WildFly WIP
> Issue Type: Bug
> Components: Security
> Reporter: Tomas Terem
> Assignee: Darran Lofthouse
> Priority: Blocker
> Labels: management
>
> Execute:
> {code:java}
> /core-service=management/management-interface=http-interface:write-attribute(name=constant-headers, value=[{path=/management, headers=[{name=A:B, value=C}]}])
> {code}
> Response now has header 'A' with value 'B: C', but user wanted header 'A:B' with value 'C'. Colon can't be part of the header name, so users should be warned about it and no headers should be added.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (WFWIP-269) Headers should not be added if header name contains a colon
by Tomas Terem (Jira)
[ https://issues.jboss.org/browse/WFWIP-269?page=com.atlassian.jira.plugin.... ]
Tomas Terem updated WFWIP-269:
------------------------------
Summary: Headers should not be added if header name contains a colon (was: Colon in a header name doesn't show a warning)
> Headers should not be added if header name contains a colon
> -----------------------------------------------------------
>
> Key: WFWIP-269
> URL: https://issues.jboss.org/browse/WFWIP-269
> Project: WildFly WIP
> Issue Type: Bug
> Components: Security
> Reporter: Tomas Terem
> Assignee: Darran Lofthouse
> Priority: Blocker
> Labels: management
>
> Execute:
> {code:java}
> /core-service=management/management-interface=http-interface:write-attribute(name=constant-headers, value=[{path=/management, headers=[{name=A:B, value=C}]}])
> {code}
> Response now has header 'A' with value 'B: C', but user wanted header 'A:B' with value 'C'. Colon can't be part of the header name, so users should be warned about it and no headers should be added.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (DROOLS-4735) [DMN Designer] Grid performance is dire
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4735?page=com.atlassian.jira.plugi... ]
Jozef Marko 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
Environment: wildfly14 with following memory settings: {{JAVA_OPTS="-Xms64m -Xmx1024m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=1024m -Djava.net.preferIPv4Stack=true"}}
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 (/)
h3. DMN decision table
- Change column width, save and reopen (x) [^resize-column.webm] [^resized-column-save.webm]
- Search the grid (/) [^search-trough-grid.webm]
- Scroll the grid (?) scrolling seems working in reasonable time assuming number of rows, however dragging canvas is slower [^drag-scroll.webm]
- Reorder columns (x) was not able to do it, still header popups shown [^reorder-columns.webm]
- Reorder rows
- Adding column (?) adding column is reasonable time assuming table size, however displaying and hiding context menu is quite slow [^add-new-column.webm]
- Removing column (/) fine, acceptable ignoring time of showing menu reported above [^delete-column.webm]
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
Environment: wildfly14 with following memory settings: {{JAVA_OPTS="-Xms64m -Xmx1024m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=1024m -Djava.net.preferIPv4Stack=true"}}
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 (/)
h3. DMN decision table
- Change column width, save and reopen (x) [^resize-column.webm] [^resized-column-save.webm]
- Search the grid (/) [^search-trough-grid.webm]
- Scroll the grid (?) scrolling seems working in reasonable time assuming number of rows, however dragging canvas is slower [^drag-scroll.webm]
- Reorder columns
- Reorder rows
- Adding column (?) adding column is reasonable time assuming table size, however displaying and hiding context menu is quite slow [^add-new-column.webm]
- Removing column (/) fine, acceptable ignoring time of showing menu reported above [^delete-column.webm]
> [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
> Attachments: aTable.dmn, add-new-column.webm, delete-column.webm, drag-scroll.webm, dtable-500-rows.dmn, reorder-columns.webm, resize-column.webm, resized-column-save.webm, search-trough-grid.webm
>
>
> 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
> Environment: wildfly14 with following memory settings: {{JAVA_OPTS="-Xms64m -Xmx1024m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=1024m -Djava.net.preferIPv4Stack=true"}}
> 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 (/)
> h3. DMN decision table
> - Change column width, save and reopen (x) [^resize-column.webm] [^resized-column-save.webm]
> - Search the grid (/) [^search-trough-grid.webm]
> - Scroll the grid (?) scrolling seems working in reasonable time assuming number of rows, however dragging canvas is slower [^drag-scroll.webm]
> - Reorder columns (x) was not able to do it, still header popups shown [^reorder-columns.webm]
> - Reorder rows
> - Adding column (?) adding column is reasonable time assuming table size, however displaying and hiding context menu is quite slow [^add-new-column.webm]
> - Removing column (/) fine, acceptable ignoring time of showing menu reported above [^delete-column.webm]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (DROOLS-4735) [DMN Designer] Grid performance is dire
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4735?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4735:
--------------------------------
Attachment: reorder-columns.webm
> [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
> Attachments: aTable.dmn, add-new-column.webm, delete-column.webm, drag-scroll.webm, dtable-500-rows.dmn, reorder-columns.webm, resize-column.webm, resized-column-save.webm, search-trough-grid.webm
>
>
> 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
> Environment: wildfly14 with following memory settings: {{JAVA_OPTS="-Xms64m -Xmx1024m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=1024m -Djava.net.preferIPv4Stack=true"}}
> 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 (/)
> h3. DMN decision table
> - Change column width, save and reopen (x) [^resize-column.webm] [^resized-column-save.webm]
> - Search the grid (/) [^search-trough-grid.webm]
> - Scroll the grid (?) scrolling seems working in reasonable time assuming number of rows, however dragging canvas is slower [^drag-scroll.webm]
> - Reorder columns
> - Reorder rows
> - Adding column (?) adding column is reasonable time assuming table size, however displaying and hiding context menu is quite slow [^add-new-column.webm]
> - Removing column (/) fine, acceptable ignoring time of showing menu reported above [^delete-column.webm]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (DROOLS-4735) [DMN Designer] Grid performance is dire
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4735?page=com.atlassian.jira.plugi... ]
Jozef Marko 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
Environment: wildfly14 with following memory settings: {{JAVA_OPTS="-Xms64m -Xmx1024m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=1024m -Djava.net.preferIPv4Stack=true"}}
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 (/)
h3. DMN decision table
- Change column width, save and reopen (x) [^resize-column.webm] [^resized-column-save.webm]
- Search the grid (/) [^search-trough-grid.webm]
- Scroll the grid (?) scrolling seems working in reasonable time assuming number of rows, however dragging canvas is slower [^drag-scroll.webm]
- Reorder columns
- Reorder rows
- Adding column (?) adding column is reasonable time assuming table size, however displaying and hiding context menu is quite slow [^add-new-column.webm]
- Removing column (/) fine, acceptable ignoring time of showing menu reported above [^delete-column.webm]
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
Environment: wildfly14 with following memory settings: {{JAVA_OPTS="-Xms64m -Xmx1024m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=1024m -Djava.net.preferIPv4Stack=true"}}
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 (/)
h3. DMN decision table
- Change column width, save and reopen (x) [^resize-column.webm] [^resized-column-save.webm]
- Search the grid (/) [^search-trough-grid.webm]
- Scroll the grid (?) scrolling seems working in reasonable time assuming number of rows, however dragging canvas is slower [^drag-scroll.webm]
- Reorder columns
- Reorder rows
- Adding column (?) adding column is reasonable time assuming table size, however displaying and hiding context menu is quite slow [^add-new-column.webm]
- Removing column (/) fine, acceptable ignoring time of showing menu reported above
> [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
> Attachments: aTable.dmn, add-new-column.webm, delete-column.webm, drag-scroll.webm, dtable-500-rows.dmn, resize-column.webm, resized-column-save.webm, search-trough-grid.webm
>
>
> 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
> Environment: wildfly14 with following memory settings: {{JAVA_OPTS="-Xms64m -Xmx1024m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=1024m -Djava.net.preferIPv4Stack=true"}}
> 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 (/)
> h3. DMN decision table
> - Change column width, save and reopen (x) [^resize-column.webm] [^resized-column-save.webm]
> - Search the grid (/) [^search-trough-grid.webm]
> - Scroll the grid (?) scrolling seems working in reasonable time assuming number of rows, however dragging canvas is slower [^drag-scroll.webm]
> - Reorder columns
> - Reorder rows
> - Adding column (?) adding column is reasonable time assuming table size, however displaying and hiding context menu is quite slow [^add-new-column.webm]
> - Removing column (/) fine, acceptable ignoring time of showing menu reported above [^delete-column.webm]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (DROOLS-4735) [DMN Designer] Grid performance is dire
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4735?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4735:
--------------------------------
Attachment: delete-column.webm
> [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
> Attachments: aTable.dmn, add-new-column.webm, delete-column.webm, drag-scroll.webm, dtable-500-rows.dmn, resize-column.webm, resized-column-save.webm, search-trough-grid.webm
>
>
> 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
> Environment: wildfly14 with following memory settings: {{JAVA_OPTS="-Xms64m -Xmx1024m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=1024m -Djava.net.preferIPv4Stack=true"}}
> 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 (/)
> h3. DMN decision table
> - Change column width, save and reopen (x) [^resize-column.webm] [^resized-column-save.webm]
> - Search the grid (/) [^search-trough-grid.webm]
> - Scroll the grid (?) scrolling seems working in reasonable time assuming number of rows, however dragging canvas is slower [^drag-scroll.webm]
> - Reorder columns
> - Reorder rows
> - Adding column (?) adding column is reasonable time assuming table size, however displaying and hiding context menu is quite slow [^add-new-column.webm]
> - Removing column
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (DROOLS-4735) [DMN Designer] Grid performance is dire
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4735?page=com.atlassian.jira.plugi... ]
Jozef Marko 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
Environment: wildfly14 with following memory settings: {{JAVA_OPTS="-Xms64m -Xmx1024m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=1024m -Djava.net.preferIPv4Stack=true"}}
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 (/)
h3. DMN decision table
- Change column width, save and reopen (x) [^resize-column.webm] [^resized-column-save.webm]
- Search the grid (/) [^search-trough-grid.webm]
- Scroll the grid (?) scrolling seems working in reasonable time assuming number of rows, however dragging canvas is slower [^drag-scroll.webm]
- Reorder columns
- Reorder rows
- Adding column (?) adding column is reasonable time assuming table size, however displaying and hiding context menu is quite slow [^add-new-column.webm]
- Removing column (/) fine, acceptable ignoring time of showing menu reported above
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
Environment: wildfly14 with following memory settings: {{JAVA_OPTS="-Xms64m -Xmx1024m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=1024m -Djava.net.preferIPv4Stack=true"}}
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 (/)
h3. DMN decision table
- Change column width, save and reopen (x) [^resize-column.webm] [^resized-column-save.webm]
- Search the grid (/) [^search-trough-grid.webm]
- Scroll the grid (?) scrolling seems working in reasonable time assuming number of rows, however dragging canvas is slower [^drag-scroll.webm]
- Reorder columns
- Reorder rows
- Adding column (?) adding column is reasonable time assuming table size, however displaying and hiding context menu is quite slow [^add-new-column.webm]
- Removing column
> [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
> Attachments: aTable.dmn, add-new-column.webm, delete-column.webm, drag-scroll.webm, dtable-500-rows.dmn, resize-column.webm, resized-column-save.webm, search-trough-grid.webm
>
>
> 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
> Environment: wildfly14 with following memory settings: {{JAVA_OPTS="-Xms64m -Xmx1024m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=1024m -Djava.net.preferIPv4Stack=true"}}
> 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 (/)
> h3. DMN decision table
> - Change column width, save and reopen (x) [^resize-column.webm] [^resized-column-save.webm]
> - Search the grid (/) [^search-trough-grid.webm]
> - Scroll the grid (?) scrolling seems working in reasonable time assuming number of rows, however dragging canvas is slower [^drag-scroll.webm]
> - Reorder columns
> - Reorder rows
> - Adding column (?) adding column is reasonable time assuming table size, however displaying and hiding context menu is quite slow [^add-new-column.webm]
> - Removing column (/) fine, acceptable ignoring time of showing menu reported above
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (WFWIP-269) Colon in a header name doesn't show a warning
by Tomas Terem (Jira)
[ https://issues.jboss.org/browse/WFWIP-269?page=com.atlassian.jira.plugin.... ]
Tomas Terem updated WFWIP-269:
------------------------------
Description:
Execute:
{code:java}
/core-service=management/management-interface=http-interface:write-attribute(name=constant-headers, value=[{path=/management, headers=[{name=A:B, value=C}]}])
{code}
Response now has header 'A' with value 'B: C', but user wanted header 'A:B' with value 'C'. Colon can't be part of the header name, so users should be warned about it and no headers should be added.
was:
Execute:
{code:java}
/core-service=management/management-interface=http-interface:write-attribute(name=constant-headers, value=[{path=/management, headers=[{name=A:B, value=C}]}])
{code}
Reponse now has header 'A' with value 'B: C', but user wanted header 'A:B' with value 'C'. Colon can't be part of the header name, but users should at least see a warning describing this behaviour.
> Colon in a header name doesn't show a warning
> ---------------------------------------------
>
> Key: WFWIP-269
> URL: https://issues.jboss.org/browse/WFWIP-269
> Project: WildFly WIP
> Issue Type: Bug
> Components: Security
> Reporter: Tomas Terem
> Assignee: Darran Lofthouse
> Priority: Blocker
> Labels: management
>
> Execute:
> {code:java}
> /core-service=management/management-interface=http-interface:write-attribute(name=constant-headers, value=[{path=/management, headers=[{name=A:B, value=C}]}])
> {code}
> Response now has header 'A' with value 'B: C', but user wanted header 'A:B' with value 'C'. Colon can't be part of the header name, so users should be warned about it and no headers should be added.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months