I just want to ask if these can affect performance of the application? Recently we did an performance enhancement of an application so far there are less logs of SlowSQL in the service center after the enhancement but base on the APDEX score it went down after the enhancement. We usually call the "IsOn" action once needed, does using that condition on a web block affect the performance? Should we just use site property instead of Feature Toggle?
It's should not affect that much, because there is also a caching mechanism in place afaik.However, it should be noted that your feature toggles should also be short-lived.
Thanks for the info, but if having to many feature toggle keys in one module or even screen would that affect the performance of the application?
It might not, but it also based on your logics, where you implement them.
If there is less use or the module has minimal components, you can use Site properties to enable/disable a feature or screen.
Thank You.
Hello Rogelio,In order to improve application performance, feature toggle allows you to check features in client side.
Be aware that this does not replace the server side check at all but it will enhance performance for sure.
What it does is, it syncs the features into a local variable and the check is done against that local variable (its a JSON array). It has a short live, so every a couple of minutes it will be re-synced with unique keys. The sync should happen right after login.
When an action is performed, it is strongly advised to check if the feature is on on the server side.
Other than this, you can check the feature directly in the server, it is cached.
Cheers!