Running a job causes retrieval of full history of job executions

[glaz666]

When running a job via SimpleJobLauncher#run , it creates new JobExecution, but retrieves all executions of the job from database:

spring-batch/spring-batch-core/src/main/java/org/springframework/batch/core/repository/support/SimpleJobRepository.java

Line 116 in f5041e6

List<JobExecution> executions = jobExecutionDao.findJobExecutions(jobInstance);

The approach to create new executions should be revised towards constant timing and constant memory usage regardless of how many times a job was executed in past.

My proposal would be to change a query to limit response size, e.g. last execution is enough to make a decision if running job instance exist.

[ioanadinuit]

Hi, is there any plan to make this enhancement? I would be happy to contribute.

[fmbenhassine]

@glaz666 I think the retrieval of job executions is required to validate a few conditions (see here). But if we find a way to improve the performance of that part without introducing any regression, I am all for it!

@ioanadinuit Thank you for your offer to help! Sure, you are welcome to contribute if you want.

[fmbenhassine]

A good start on this issue is to provide a minimal example that we can use to validate the performance issue and also as a comparison baseline with the improved version.