You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@batchee.apache.org by "Mark Struberg (JIRA)" <ji...@apache.org> on 2016/08/31 09:45:20 UTC

[jira] [Resolved] (BATCHEE-107) JobOperator#getJobNames() is slow if many Batches exist

     [ https://issues.apache.org/jira/browse/BATCHEE-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Struberg resolved BATCHEE-107.
-----------------------------------
    Resolution: Fixed

> JobOperator#getJobNames() is slow if many Batches exist
> -------------------------------------------------------
>
>                 Key: BATCHEE-107
>                 URL: https://issues.apache.org/jira/browse/BATCHEE-107
>             Project: BatchEE
>          Issue Type: Bug
>          Components: jbatch-core
>    Affects Versions: 0.3-incubating
>            Reporter: Mark Struberg
>            Assignee: Mark Struberg
>             Fix For: 0.4-incubating
>
>
> We have many Batches in our JobInstance table. This heavily slows down the current implementation of JobOperator#getJobNames().
> The current impl reads through all the values and performs a SecurityService check on each single batch run. That means we read in all 200k job instances just for getting the available jobNames...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)