When would you need to flush cache? The obvious answer is when there is a
workflow change on production.. Changes to workflow are done whenever there
is need for code change for enhancement or bug fixes.. The general industry
practice is to manage these changes in a change window, where there is a
scheduled outage, which is typically scheduled on weekends or the least
productive hours of an organization. So cache should be flushed during these
changes.
That being said, there may be emergency changes that were a result of a part
or whole system being rendered unusable pending that change. On such an
event it would be ok to flush your cache after fixing whatever the
problem/bug/enhancement was.
Yes flushing cache during production hours may cause a brief negative impact
on users using the system at the time of the change.
Joe
-----Original Message-----
From: David Durling
Sent: Monday, March 26, 2012 3:48 PM Newsgroups:
public.remedy.arsystem.general
To: arslist@ARSLIST.ORG
Subject: Effects of flushing midtier cache
Hi,
I'm one of those that has found it necessary to use the "flush cache" button
in the mid tier config when sometimes certain changes aren't picked up at
the regular cache check interval.
Do you all consider a flush of the mid tier cache to be unintrusive -
something that can be done during production hours? Or is it something that
should be done off-hours?
On our server I don't notice performance issues in using it, and in what
little testing I've done, user sessions seem to be uninterrupted. (I'm not
sure about floating users on the web, though - if there's anything to
consider there.)
I'm on ARS 7.5 patch 007 with mid tier 7.5 patch 007 with apache/tomcat.
Thanks,
David
---
David Durling durl...@uga.edu
Enterprise IT Services
University of Georgia
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
