which one performs better - sys_properties with ignore cache=true OR GlideRecord

[ceskie]

Ahoy,

My question: is running GlideRecord get() method on a custom table as fast as calling gs.getProperty() when the property has ignore_cache=true? Can gs.getProperty be replaced with .get() in this case?

Background: in our environment, we are not allowed to perform any changes in PROD instance, punctum. This means we are also forbidden to update any sys_properties. Often comes a situation that we need to do that and to perform sys_property change, we must undergo entire release process (update property in sub dev, capture update in the update set, push the update set to master dev, release to app repo, install in UAT, wait 24 h, install in PROD). This process takes often 2 days. I am about to create custom, scoped table for frequently changed configurations and a Class which will basically mimic gs.getProperty(name, default value). My concern is obvious - can this have any potential performance impact, running GlideRecord frequently?

Thank you for any input!

[Community Alums]

Hi @ceskie ,

As you already aware that gs.getProperty is a Server Side way to get the value stored in a system property.

As per the scenario you mentioned, it's better to go with gs.getProperty() while the property has ignore_cache=true rather then GlideRecord get().

Mark my answer correct & Helpful, if Applicable.

Thanks,
Sandeep

[Community Alums]

Hi @ceskie ,

Any update to this ?Any follow-up required? if not

Kindly mark the answer as Correct & Helpful both such that others can get help.

Thanks,
Sandeep

[Chandu Telu]

Hi,

 is running GlideRecord get() method on a custom table as fast as calling gs.getProperty() when the property has ignore_cache=true? -  There is no much difference on fast if use this in server side but 

using gs.property is best practice but in your scenario you can use the GlideRecord with get method

@Ankur Bawiskar  : Need your help here

Thanks
Chandu Telu
Please Mark ✅ Correct/helpful, if applicable,

[ceskie]

Thank you, we will put it into test. I will eventually post update next week how does it perform (we are using gs.getProperty in our scoped app lets say ~25 M times a day so we will replace that with GlideRecord get because of reasons above).