@MillieB16852873 @AnggunMD here is the response given by our support engineer.

If you require further follow-up I suggest you log a support incident to discuss this further with our support team:

"

Here are the answers to GOS queries:

1. What is the difference between manual recompile and automatic recompile (if the config is SMART_CACHE)?

[Pega] As Globally Optimized Strategy (GOS) inline all the underlying rules and generates a global SSA program, GOS needs to listen to changes of all the underlying rules. If any inline rule is checked out/saved/checked in/discarded or a new version of it is imported into the system, the generated GOS program will be ditched and a new one will be generated when then GOS is invoked again. This is the default behavior of GOS and the whole listen-throw away-regenerate cycle happens automatically behind the scenes.    GOS program generation takes time. Thus users can choose to turn off the GOS program auto re-compile (by tuning a Dynamic System Settings, aka DSS) and then take care of manually recompiling the GOS's they are interested in. In that case, the GOS program will not re-compile automatically if any inline rules are updated in the environment. Instead, the user needs to trigger it manually by saving the GOS rule or going to "Strategy Optimizations" landing page and clicking on "Recompile".   Note: Only disable automatic recompilation on environments where rules are not frequently updated and performance is important, for example, on production environments. And whenever you propagate the changes manually, and then recompile GOS rules on the destination environment.   The steps are available below; which you need to test in the UAT environment thoroughly before implementing into Production.   https://docs-previous.pega.com/decision-management/86/frequently-asked-questions-about-globally-optimized-strategies https://docs-previous.pega.com/decision-management/86/understanding-globally-optimized-strategies   It is Developer's responsibility to import GOS along with its inline rules to the destination system or trigger GOS re-compile manually on the destination system. This is especially important if GOS auto-recompilation is turned off on the destination system.

2. Why can the automatic recompile (SMART_CACHE) run even though the GOS is in the ruleset, which is locked?  

[Pega] The automatic recompile (SMART_CACHE) ; as explained in #1 above, it is managed internally within our code unlike Manual compilation.

Disabling the GOS recompile in Production would require regular monitoring / manual compiling of the strategy every time an update is applied. Not something we generally recommend as a long term solution.

We would also like to know your upgrade plans.

Kindly note that the GOS compilation has been enhanced in latest Pege release. i.e. Pega 8.8.3. where it enhances the Pega's REST Service's Circuit Breaker (aka 'service SLA with fallback activity') logic to allow it to start in open mode (instead of closed, which is the current default). When the Circuit Breaker starts in open mode (a.k.a. broken) the initial requests will execute the fallback activity allowing the node to do it's initial warmup (i.e. classloading, rule compilation) before it starts running the primary activity. After the initial retry interval elapses a single request is allowed to execute the primary activity. When it completes successfully, Circuit Breaker closes and all traffic is routed to the primary activity.   If you upgrade to Pega 8.8.3., you will be able to benefit out of this enhancement."