[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
- Save and reopen (x) not able to save in reasonable time
- Change column width (/)
- Search the grid (/)
- Scroll the grid (/)
- Reorder columns (/)
- Reorder rows (/)
- Adding column (/)
- Removing column (/)
- Edit the cell (/)
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
- Save and reopen (x) not able to save in reasonable time
- Change column width (/)
- Search the grid (/) [^search-trough-grid.webm]
- Scroll the grid (/)
- Reorder columns (x) was not able to do it, still header popups shown [^reorder-columns.webm]
- Reorder rows (/) assuming performance of other actions and size of the table [^reorder-rows.webm]
- Adding column (/)
- Removing column (/)
- Edit the cell (/)
> [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, dtable-500-rows.dmn, reorder-columns.webm, reorder-rows.webm, resized-column-save.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
> - Save and reopen (x) not able to save in reasonable time
> - Change column width (/)
> - Search the grid (/)
> - Scroll the grid (/)
> - Reorder columns (/)
> - Reorder rows (/)
> - Adding column (/)
> - Removing column (/)
> - Edit the cell (/)
--
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
- Save and reopen (x) not able to save in reasonable time
- Change column width (/)
- Search the grid (/) [^search-trough-grid.webm]
- Scroll the grid (/)
- Reorder columns (x) was not able to do it, still header popups shown [^reorder-columns.webm]
- Reorder rows (/) assuming performance of other actions and size of the table [^reorder-rows.webm]
- Adding column (/)
- Removing column (/)
- Edit the cell (/)
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
- Save and reopen (x) not able to save in reasonable time
- Change column width (/)
- Search the grid (/) [^search-trough-grid.webm]
- Scroll the grid (/)
- Reorder columns (x) was not able to do it, still header popups shown [^reorder-columns.webm]
- Reorder rows (/) assuming performance of other actions and size of the table [^reorder-rows.webm]
- Adding column (x)
- Removing column (/) fine, acceptable ignoring time of showing menu reported above [^delete-column.webm]
- Edit the cell (/)
> [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, dtable-500-rows.dmn, reorder-columns.webm, reorder-rows.webm, resized-column-save.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
> - Save and reopen (x) not able to save in reasonable time
> - Change column width (/)
> - Search the grid (/) [^search-trough-grid.webm]
> - Scroll the grid (/)
> - Reorder columns (x) was not able to do it, still header popups shown [^reorder-columns.webm]
> - Reorder rows (/) assuming performance of other actions and size of the table [^reorder-rows.webm]
> - Adding column (/)
> - Removing column (/)
> - Edit the cell (/)
--
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: (was: add-new-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, dtable-500-rows.dmn, reorder-columns.webm, reorder-rows.webm, resized-column-save.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
> - Save and reopen (x) not able to save in reasonable time
> - Change column width (/)
> - Search the grid (/) [^search-trough-grid.webm]
> - Scroll the grid (/)
> - Reorder columns (x) was not able to do it, still header popups shown [^reorder-columns.webm]
> - Reorder rows (/) assuming performance of other actions and size of the table [^reorder-rows.webm]
> - Adding column (/)
> - Removing column (/)
> - Edit the cell (/)
--
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: (was: 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, dtable-500-rows.dmn, reorder-columns.webm, reorder-rows.webm, resized-column-save.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
> - Save and reopen (x) not able to save in reasonable time
> - Change column width (/)
> - Search the grid (/) [^search-trough-grid.webm]
> - Scroll the grid (/)
> - Reorder columns (x) was not able to do it, still header popups shown [^reorder-columns.webm]
> - Reorder rows (/) assuming performance of other actions and size of the table [^reorder-rows.webm]
> - Adding column (/)
> - Removing column (/)
> - Edit the cell (/)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (WFWIP-272) Specifying header name containing '\'n in constant-headers causes fatal error
by Darran Lofthouse (Jira)
[ https://issues.jboss.org/browse/WFWIP-272?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse commented on WFWIP-272:
----------------------------------------
For header names we have a description of allowed values here: -
https://tools.ietf.org/html/rfc2616#page-15
https://tools.ietf.org/html/rfc2616#page-31
I am going to go ahead and add validation that the names specified correspond to the definition.
> Specifying header name containing '\'n in constant-headers causes fatal error
> -----------------------------------------------------------------------------
>
> Key: WFWIP-272
> URL: https://issues.jboss.org/browse/WFWIP-272
> Project: WildFly WIP
> Issue Type: Bug
> Components: Security
> Reporter: Tomas Terem
> Assignee: Darran Lofthouse
> Priority: Blocker
> Labels: management
>
> Specifying header name containing '\'n in constant-headers causes fatal error:
> {code:java}
> 10:02:36,853 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service org.wildfly.management.http.extensible: org.jboss.msc.service.StartException in service org.wildfly.management.http.extensible: WFLYSRV0083: Failed to start the http-interface service
> at org.jboss.as.server.mgmt.UndertowHttpManagementService.start(UndertowHttpManagementService.java:393)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalArgumentException: UT000149: HttpString is not allowed to contain newlines. value: A
> B
> at io.undertow.util.HttpString.checkForNewlines(HttpString.java:126)
> at io.undertow.util.HttpString.<init>(HttpString.java:120)
> at io.undertow.util.HttpString.<init>(HttpString.java:103)
> at org.jboss.as.domain.http.server.StaticHeadersHandler$HeaderConstant.<init>(StaticHeadersHandler.java:70)
> at org.jboss.as.domain.http.server.StaticHeadersHandler.addHeader(StaticHeadersHandler.java:61)
> at org.jboss.as.domain.http.server.ManagementHttpServer.setupOpenListener(ManagementHttpServer.java:369)
> at org.jboss.as.domain.http.server.ManagementHttpServer.create(ManagementHttpServer.java:279)
> at org.jboss.as.domain.http.server.ManagementHttpServer.access$2600(ManagementHttpServer.java:111)
> at org.jboss.as.domain.http.server.ManagementHttpServer$Builder.build(ManagementHttpServer.java:666)
> at org.jboss.as.server.mgmt.UndertowHttpManagementService.start(UndertowHttpManagementService.java:351)
> ... 8 more
> 10:02:36,856 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("core-service" => "management"),
> ("management-interface" => "http-interface")
> ]) - failure description: {"WFLYCTL0080: Failed services" => {"org.wildfly.management.http.extensible" => "WFLYSRV0083: Failed to start the http-interface service
> Caused by: java.lang.IllegalArgumentException: UT000149: HttpString is not allowed to contain newlines. value: A
> B"}}
> 10:02:36,856 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("core-service" => "management"),
> ("management-interface" => "http-interface")
> ]) - failure description: {"WFLYCTL0080: Failed services" => {"org.wildfly.management.http.extensible" => "WFLYSRV0083: Failed to start the http-interface service
> Caused by: java.lang.IllegalArgumentException: UT000149: HttpString is not allowed to contain newlines. value: A
> B"}}
> 10:02:36,868 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> 10:02:36,875 INFO [org.jboss.as] (MSC service thread 1-5) WFLYSRV0050: WildFly Core 11.0.0.Beta3-SNAPSHOT stopped in 3ms
> {code}
--
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
- Save and reopen (x) not able to save in reasonable time
- Change column width (/)
- Search the grid (/) [^search-trough-grid.webm]
- Scroll the grid (/)
- Reorder columns (x) was not able to do it, still header popups shown [^reorder-columns.webm]
- Reorder rows (/) assuming performance of other actions and size of the table [^reorder-rows.webm]
- Adding column (x)
- Removing column (/) fine, acceptable ignoring time of showing menu reported above [^delete-column.webm]
- Edit the cell (/)
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
- Save and reopen (x) not able to save in reasonable time
- Change column width (/)
- Search the grid (/) [^search-trough-grid.webm]
- Scroll the grid (/)
- Reorder columns (x) was not able to do it, still header popups shown [^reorder-columns.webm]
- Reorder rows (/) assuming performance of other actions and size of the table [^reorder-rows.webm]
- 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 (/)
> [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, dtable-500-rows.dmn, reorder-columns.webm, reorder-rows.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
> - Save and reopen (x) not able to save in reasonable time
> - Change column width (/)
> - Search the grid (/) [^search-trough-grid.webm]
> - Scroll the grid (/)
> - Reorder columns (x) was not able to do it, still header popups shown [^reorder-columns.webm]
> - Reorder rows (/) assuming performance of other actions and size of the table [^reorder-rows.webm]
> - Adding column (x)
> - Removing column (/) fine, acceptable ignoring time of showing menu reported above [^delete-column.webm]
> - Edit the cell (/)
--
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
- Save and reopen (x) not able to save in reasonable time
- Change column width (/)
- Search the grid (/) [^search-trough-grid.webm]
- Scroll the grid (/)
- Reorder columns (x) was not able to do it, still header popups shown [^reorder-columns.webm]
- Reorder rows (/) assuming performance of other actions and size of the table [^reorder-rows.webm]
- 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 (/)
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
- Save and reopen (x) not able to save in reasonable time
- Change column width (/)
- Search the grid (/) [^search-trough-grid.webm]
- Scroll the grid (/)
- Reorder columns (x) was not able to do it, still header popups shown [^reorder-columns.webm]
- Reorder rows (/) assuming performance of other actions and size of the table [^reorder-rows.webm]
- 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]
> [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, dtable-500-rows.dmn, reorder-columns.webm, reorder-rows.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
> - Save and reopen (x) not able to save in reasonable time
> - Change column width (/)
> - Search the grid (/) [^search-trough-grid.webm]
> - Scroll the grid (/)
> - Reorder columns (x) was not able to do it, still header popups shown [^reorder-columns.webm]
> - Reorder rows (/) assuming performance of other actions and size of the table [^reorder-rows.webm]
> - 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 (/)
--
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: (was: 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, delete-column.webm, dtable-500-rows.dmn, reorder-columns.webm, reorder-rows.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
> - Save and reopen (x) not able to save in reasonable time
> - Change column width (/)
> - Search the grid (/) [^search-trough-grid.webm]
> - Scroll the grid (/)
> - Reorder columns (x) was not able to do it, still header popups shown [^reorder-columns.webm]
> - Reorder rows (/) assuming performance of other actions and size of the table [^reorder-rows.webm]
> - 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 (/)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months