Is there really any impact when we commit an update set during business hours?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-17-2024 11:58 PM - edited 06-18-2024 05:56 AM
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?)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-18-2024 12:20 AM
ideally code migration to prod should be done in non business hours so that there is no performance impact.
it varies from customer to customer
If my response helped please mark it correct and close the thread so that it benefits future readers.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-18-2024 05:57 AM
@Ankur Bawiskar @Sandeep Rajput
My question is not on best practice, but my question is -
1, How come we are not facing any issues a we are committing the update sets left and right?
2. 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?)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-18-2024 06:11 AM
my responses inline
1, How come we are not facing any issues a we are committing the update sets left and right? -> it depends on what your update set has; if it has complex business logic and workflows etc; it will cause issue as it might break any existing working business logic/process. But that's not defined that you will always face issue.
2. 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?) -> I don't think any way to check that
If my response helped please mark it correct and close the thread so that it benefits future readers.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-18-2024 10:21 AM
@Ankur Bawiskar Thanks for replying.
I am talking about point 'c' in this article What can cause a full system cache flush - Support and Troubleshooting (servicenow.com) which says deploying update sets will cause cache flush. and ofcoure when cache flush happens, everything has to be rebuilt which inturn causes performacne issues.
My question is wrt above point 🙂
Hope atleast now its clear as to what I am asking.