nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

When does TeamSite release cache?

kriv

According to iwstat -c, TeamSite never significantly releases cache in our implementation. We have 200,000 cache configured, and during the day cache increases all day until midnight when iwserver is taken offline for a backup. Restarting iwserver sets cache back to zero.

KB article #1344 says iwfreeze will free cache but it never seems to as indicated by iwstat -c.

TS 6.1 SP2
Win2000

Find more posts tagged with

Comments

ccprofessional

What is the problem you are seeing?

Nicholas

Send the output of iwstat -c

Are you facing slowness?

-- Nicholas

kriv

We solved the issue by getting a better understanding of TS cache. Basically, cache is not released until it is full, at which point it frees 10,000 back into the pool. With 4Mb per cache point, we were seeing a lot of memory get used when our cache would get near the set point (200,000 which is about 800 Mb).

Resolution was first recognizing that our content store was corrupt, and had been for some time. When TS would hit one of these corruption points, it would touch a lot of files loading up the cache. Second, we increased the memory in the server (alternatively, would could have decreased the cache setting to 100,000) so that when cache was high and taking up tons of memory, other memory wasn't being swapped to disk. As I understand it, Windows reserves a chunk of memory for itself, but doesn't really tell you that. If you don't allow extra memory for the OS, performance degrades.

Bottomline: issue is resolved.

AK