Task deletion performance with a high number of baselines

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

Task deletion performance degradation when a large number of baselines exist and the task to be deleted is part of them

STEPS TO REPRODUCE:

1. Create a project with 01/01/23 till 31/12/26 dates
2. Add about 40 team members
3. Create about 60 tasks and assign every team member to the tasks
4. Go to project baselines and create about 20 baselines
5. Go to the tasks list and try to delete a tasks

Expected results: The task should get deleted on a resonable time
Actual results: The task deletion can last 20-30 minutes or longer even if the size of the project is big

Environment

Clarity 16.1.1, 16.1.2

Cause

This is caused by DE69937

Resolution

Engineering has analyzed this.

In the scenario mentioned in the KB (40 team members, 60 tasks, and 20 baselines) the task deletion takes about 5 minutes. This is due to around 73000 SQL executes, mostly related to slice deletion. This is as Clarity is currently designed to handle these recursive deletions. 

The bigger the number of baseline deletion execution, the longer the task deletion might take.

This area has been refactored through a user story to handle deletions in the background- The user story was implemented in 16.1.3

Additional Information

If baselines are deleted, the task gets deleted instantaneously 

However, on the scenario described above, deleting baselines from the UI is also taking a long time.