Couple of issues with large number of jobs:
- When user runs a jobflow with 10k+ jobs and attempts to view that job in Execution history, CloverETL Server UI crashes with Java Exception Out of Heap Space or with GC overhead limit exceeded. Can we optimize UI to do the loads of information more selectively (I am not sure much gets loaded into memory and what is really needed)?
- Archivator should allow to filter the purge of Execution history also by JobName. Users often want to clean-up FINISHED_OK often running jobs but keep faild or sparsly running jobs in Execution history for a longer time.