- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-24-2018 10:32 AM
Hello,
We previously implemented Standard Change and we began implementing more simplistic changes into production more often. Originally, we were doing this at any time of day, but our architect pointed out that committing update sets automatically flushes the cache which can affect performance, so we began implementing them after business hours. Recently, it has come up that update sets do not actually flush the cache and that we can go back to committing them at any time. I have not been able to find anything definitive regarding this.
Does committing update sets automatically flush the cache? Is it safe for us to implement our standard changes during the work day?
Thanks for the help!
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-24-2018 07:27 PM
Hello Bryson,
The best practice is to avoid committing an update set to a production instance during business hours. The instance may perform slower temporarily as the update set applies.
Reference:
https://docs.servicenow.com/bundle/istanbul-application-development/page/build/system-update-sets/task/t_PlanTheUpdateProcessForUpdateSets.html
http://blog.symfoniesm.com/cache-flushing-performance-impact-in-servicenow
Thanks,
Pradeep Sharma

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-24-2018 07:27 PM
Hello Bryson,
The best practice is to avoid committing an update set to a production instance during business hours. The instance may perform slower temporarily as the update set applies.
Reference:
https://docs.servicenow.com/bundle/istanbul-application-development/page/build/system-update-sets/task/t_PlanTheUpdateProcessForUpdateSets.html
http://blog.symfoniesm.com/cache-flushing-performance-impact-in-servicenow
Thanks,
Pradeep Sharma