we don´t have many features to control what is within the cache, apart from flushing it completely.
I think when you restart the process there is some work being applied to the cached files in regards to building an index etc., which is pretty CPU intensive - I assume this is working as expected, but certainly it would make sense to not eat up all resources while working with the cache, but maybe take longer for doing the cache related tasks (with limited resource utilization), and probably bypass the cache until it is ready (or something similar to this approach).
Just for our information, did you file an SR with support on this topic? It would be interesting if there is maybe something within the cache that would cause this behavior and support may be the right guys to investigate.
I have not heard similar complaints, but for me it sounds logical in some way. I would be interested as well if others have seen this behavior.
Thanks for sharing.
I have a customer with a similar problem. When a user intially open their browser and goes to Google it will take 15-20 seconds to load. After the intial wait performance is fine unless they say off the Internet for awhile then it will reappear once they open their browser. They do have a support ticket open.
After re-flushing the cache, we had no performance issues afterrestarting MWG services.
We have re-sized the cache partition to 70 Gigs and now the cachetops out at 50 Gigs ( I am assuming 70% of available partitionspace is configured ) - I have restarted the MWG services when cacheis full and there is no performance issues observed.
Additionally the Cache Efficiency is 21% Hit - which is acceptableand comparable when the cache size was larger.
We have concluded that the original partition size allocated to/opt/mwg/cache was excessive, and considering I am not able tore-size the cache size in WG7, the only option was to reducepartition size. Additionally it would be advantageous if we were ableto apply additional cache configuration settings such as cachemin/max object size etc.
Please note the problem we were initially experiencing was thatafter the MWG services were re-started, it appears that the cachestart-up process ( indexing etc ) only commences immediately afterthe cache is queried with internet requests.
I have documented the process to resize the cache partition for our appliances - if you need assistance - please ask