[
https://issues.jboss.org/browse/WFLY-7418?page=com.atlassian.jira.plugin....
]
Harald Pehl commented on WFLY-7418:
-----------------------------------
One workaround could be to open another tab, browser window or different browser to avoid
blocking the rest of the management console. Not sure if that works out, though. Another
option could be the use of web workers [1], but that would need more analysis and would be
something to consider for HAL.next.
Apart from that I don't have other solutions atm.
[1]
https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Using_we...
Batch deployments with a large number of executed jobs can lock up or
slow down the web console
-----------------------------------------------------------------------------------------------
Key: WFLY-7418
URL:
https://issues.jboss.org/browse/WFLY-7418
Project: WildFly
Issue Type: Enhancement
Components: Batch, Web Console
Reporter: James Perkins
Assignee: James Perkins
Batch deployments which contain a large number of executed jobs can be extremely slow to
process as the {{/deployment=batch.war/subsystem=batch-jberet}} processes each job
instance then each job execution of that job instance.
One possibly helpful option for the web console would be to add a new description
attribute to indicate the resource may be slow to process. The web console might be able
to run a background task to populate data rather than locking up the UI. There would still
be an issue with a large memory footprint here however.
JBeret might want to consider having a way to archive jobs too rather than just purge
them. Some users may want to keep all job execution data. Archiving this data could reduce
the size of the current data being retrieved.
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)