Frequent cache flushes negatively impact instance performance.

[1_DipikaD]

Hi All,

Frequent cache flushes are happening on the instance due to a few properties being updated constantly.

Please suggest Which things need to be checked while reviewing and enabling the ignore cache for these properties. Is enabling ignore cache could be best practice for this or need to follow  different approach ?

Thank You

[Kieran Anson]

Hi,

Ignore cache will prevent a full cache flush being performed, but the system will still need to flush the cache for the system properties table so all nodes have the most up-to-date values.

If a property needs to be frequently changed, then it is likely best stored in a separate table rather than a system property to negate performance impact

[Nilesh Pol]

@1_DipikaD 

ignore_cache = true means - Don’t store this property in memory cache; always fetch it directly from the database.

Use ignore_cache = true only if:

The property changes frequently (e.g., updated by automation every few minutes).

The property is used rarely in code (not in every transaction or flow).

You want to avoid cache flushes triggered by frequent updates.

Avoid ignore_cache = true if:

The property is used in core transactions (incident creation, catalog flow, etc.).

It’s referenced often in scripts or UI actions — because every retrieval will hit the database, causing performance overhead.

[Kieran Anson]

ignore_cache does not mean the property is not stored in memory cache, all properties are cached

[Ankur Bawiskar]

@1_DipikaD 

I agree with what @Kieran Anson mentioned.

If my response helped please mark it correct and close the thread so that it benefits future readers.