I am kinda curious why a time slicing job would be set up to run every 5 minutes.
isn't that a little resource heavy to run a job that much?
Is it really necessary?
It really drills down to your business requirement. A lot of functionalities depend on the Time Slicing job like your allocations, assignments, data in the report and many more. Basically your slice tables are all dependent on the time slicing job. If your business demands live data to show up in the app every 5 minutes, then TS should be run in this frequency. I have seen many customers running TS every minute because their business demands live data at any point of time.
TS job consider only the delta, meaning, it will pick only the new changes in the system and not delete the whole records and insert them back again in the table. So running this job more frequently will have very minimal records to be processed and the job completes fairly quickly.
Having said this, if you have customized job utilizing the slice tables, you should rethink about the schedule of these jobs and make a call if the custom jobs can be scheduled after hours once in a day or so.
Hope this helps
You should also verify how long the job takes. If it set it to run once a minute and it runs on average more than a minute you should try to run it less frequently to see if it has time to complete.
How long does it take now to complete?
Retrieving data ...