Achieve Process

As Stefan notes, having long archive settings to allow the use of Process Reports is not a scalable solution.  Back about 10 years ago (before the Tempo days), we had to retain all completed processes in memory for 1-3 years for reporting - the server would become unstable, we had to keep throwing  more memory at it, etc.

Now, we don't use any Process Reports, process instances are set to archive after 30 days (or less), and all is well.  Data is persisted to the DB between each step of a process and all reporting is done from the DB via a!queryEntity().  Server is happy, and I sleep much better at night.  We're just under 6 million completed tasks in the environment at this time.  

As Stefan notes, having long archive settings to allow the use of Process Reports is not a scalable solution.  Back about 10 years ago (before the Tempo days), we had to retain all completed processes in memory for 1-3 years for reporting - the server would become unstable, we had to keep throwing  more memory at it, etc.

Now, we don't use any Process Reports, process instances are set to archive after 30 days (or less), and all is well.  Data is persisted to the DB between each step of a process and all reporting is done from the DB via a!queryEntity().  Server is happy, and I sleep much better at night.  We're just under 6 million completed tasks in the environment at this time.