Is there really any impact when we commit an update set during business hours?

[Suggy]

As per this article, committing an update set will flush the cashe.

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0793295

But we have been committing update sets in production throughout the day (since many years) whenever we feel like committing, but never faced any issue till now.

Is there any evidence or is there a way for me to check the performance impact of committing the update set (which causes cache flush as per the documentation?)

[Sandeep Rajput]

@Suggy It is generally a recommend practice to make major releases on production instances during non business hours. As a lot can go wrong while releasing a major functionality on production and it may have some severe business impacts. Not all changes cause a cache flush, some of the cache flush can be attributed to the changes in the system property (On Properties that don't have the 'ignore cache' check box checked).

[Suggy]

@Sandeep Rajput 

What can cause a full system cache flush - Support and Troubleshooting (servicenow.com)

Above article clearly says 'Deploying Update sets' causes Cache flush. So are you saying this article is wrong? or am I miss understanding something 🙂

[Bert_c1]

Trust the KB article. Table schema changes can take hours, maybe days, on a production instance. However, the methods used by servicenow prevent data loss.  so it is best to run those on weekends. But the apply the same update set on a sub-prod instance recently cloned from production is best practice and can show what to expect on production.