Performance implications of “overriding” the default behavior for Case ID sequence from 1000 to 1.
We are in the process of updating our Pega environments to version 8.5.6, and with this we found that the Case ID sequencing has changed from being sequential - 1, 2, 3, 4, 5...etc. to now being like 1, 1001, 2, 2001, 3001, 3, 4, 3002... etc. We found this resource which explains what has been updated: https://support.pega.com/discussion/case-id-generation-mechanism
For some of our application teams I received feedback that the preference is to continue Case ID sequence in the current way (incrementing by 1). One concern is that the new mechanism will scale Case ID too quickly, when we already have some Case IDs in Production exceeding 100000. Another concern is around character limits in SAP where we are passing values which have Case ID concatenated with other fields.
Could any experts help to provide insight about the impact of overriding this new default behavior for Case ID? Will there be any performance degradation, or should we expect to at least maintain the same performance as we see in our environment today (and instead we will just miss the benefits that come with larger Case ID batches)?
Also just to confirm, will there be any impact on the "stale thread" issue which is resolved in 8.5.6 if we proceed to keep Case ID incrementing by 1 instead of the new default of 1000?
Bits in Glass
IN
@JoshS302 I think it would not a better move because new approach was brought in to reduce the DB hit. In the new approach, Only when node batch gets exhausted or node gets restarted DB hit will be happening. But if we change the value to 1, then again it becomes old mechanism where in again for each case creation DB hit will be there and which causes severe performance issues.