Currently, with the DC implementation, the scheduled job status and history were not cached which results in the following query has been executed on every each scheduled job execution against the database:
(example in oracle)

select * from ( select schedulerr0_.id as id1_51_, schedulerr0_.job_id as job_id2_51_, 
 schedulerr0_.start_time as start_time3_51_, schedulerr0_.duration as duration4_51_, 
 schedulerr0_.outcome as outcome5_51_, schedulerr0_.message as message6_51_ 
 from scheduler_run_details schedulerr0_ where schedulerr0_.job_id=:1 order by schedulerr0_.start_time desc ) 
 where rownum <= :2 

This is causing unnecessary database resource consumption, and in case the scheduled job cleanup job failed to execute for some reason, it might cause heavy performance issues.

It will be great to check what could be a better way to handle this data that supposed to be cached.