Clarity: Time Slicing Job Slow Performance - Taking Longer to Finish

Document ID : KB000049540
Last Modified Date : 14/02/2018
Show Technical Document Details


Last few weeks the Time Slicing job seems to have increased in the amount of time to finish processing. When running queries to count the number of records yet to be sliced, we see the counts are moving along. We noticed that after the job completed, the next time it started up; there were a large number of allocation records waiting to be sliced again. This seems to be causing the increase in the amount of time it takes to finish the job. What is going on?


Time Slicing Performance Troubleshooting Guide

If Time Slicing job seems to all of a sudden take a longer time, check the following:

  1. When the increase in processing time was observed, did someone perform a XOG Write action to add lots of projects with allocations and assignments?
    This will impact the job because new data will need to be sliced for various existing Time Slice definitions.

  2. Did someone change the Clarity Base Calendar?
    This will impact the Time Slicing job because the Base Calendar controls resource availability and this is taken into the calculation for the allocation and assignment slices.
    If this calendar is changed, the data will be triggered for a re-slice and depending on the amount of data to be re-sliced; this will impact the amount of time to complete the job.

  3. Did a 'rollover' occur? A 'roll-over' occurs at regular intervals based on the Time Slice definition.

  4. There are weekly and monthly roll over intervals.
    The Expiration Date on the Time Slice definition will indicate when the next 'rollover' is to occur.

  5. Have the DBA check/monitor the database to see if there are any other processes running that is sharing the processing time.

  6. Editing a Time Slice definition will erase the data for that slice; however the data will be replaced when the Time Slicing job is next run.
    The date range of the slice definition and the amount of data that needs to be re-sliced will impact the amount of time required for the Time Slicing job to finish.
    If you are modifying Time Slice definitions, be sure to only update one; let the job run to completion and then update another slice definition.
    This will help to minimize the amount of time required for the job to complete.

Keywords: CLARITYKB, timeslice, timeslicing, time-slice, time-slicing.