[jboss-jira] [JBoss JIRA] (WFLY-7418) Batch deployments with a large number of executed jobs can lock up or slow down the web console

[James Perkins (Jira)]

    [ https://issues.jboss.org/browse/WFLY-7418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13760229#comment-13760229 ] 

James Perkins commented on WFLY-7418:
-------------------------------------

Hi [~timonz], unfortunately I've not looked at this in some time as we've not heard of any issues with it. I had just happened to find it during testing with large amounts of batch jobs. At this point the only real workaround I'm aware of is to reduce the number of batch entries.

I suppose one option would be to add an option in the subsystem which disables the runtime batch job resources. This would mean batch jobs can't be viewed or restarted from management operations including the web console and CLI, but may be okay for large numbers of batch jobs anyway.

> 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
>            Priority: Major
>              Labels: move_to_halnext
>
> 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.12.1#712002)