search cancel

Slow Update Earned Value and Cost Totals Job Performance with SQL Curve (DE60061)


Article ID: 210316


Updated On:


Clarity PPM On Premise Clarity PPM SaaS


Performance Issue. After upgrading to 15.9.1, the Earned Value and Cost Totals job takes much longer than before. 

Steps to Reproduce:  

  1. On a pre-15.9.1 environment, run Update Earned Value and Cost Totals job. Note the time it takes 
  2. Upgrade to 15.9.1 
  3. Run the Update Earned Value and Cost Totals job again 

Expected Results: The job to run within reasonable time. 

Actual Results: The Update EV and Cost Totals job is significantly slower on 15.9.1 when SQL Curves are enabled (which is the default option). If we disable SQL Curves then it starts working fast again. 


  • This is caused by the new SQL Curves introduced in 15.9.1 - this functionality needs optimizations. 
  • It is possible for the Time Slic Sync (Time Slicing Group By) job to run while the Update Earned Value totals job runs.  Because the EVM job now nulls the SQL Curves, the Time Slice Sync job may start replacing them meaning that the two jobs will be working on the same table.   
  • This issue can also affect the performance of the 'Time Slicing' job. 
  • This issue can possibly cause a Java Heap Space error on Update Earned Value and Cost Totals job. 
  • When the workaround is implemented, the 'Time Slicing Group By' job will no longer be visible in Clarity user interface because the SQL Curves will be disabled. 


Release : 15.9.1, 15.9.2


This is DE60061, fixed in Clarity 15.9.3 and


  • None for customers who use Modern UX as we cannot disable SQL Curves for Modern UX. 
  • If you don't use Modern UX yet, disable the SQL Curves. You will have to switch it back when you start using Modern UX. 

Additional Information