Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Should I be enabling this feature on a file server?

What type of performance hit is involved with this?

I ask as its not something I can easily turn off once on.

share|improve this question
up vote 4 down vote accepted

SIS in Storage Server 2008 is only file based, not byte or block based. It's a rather emaciated SIS feature that only gives you gains if you have an enormous amount of files, and even then only if there isn't disciplined file storing and sharing habits. For example, if people scatter the same file over and over all over the server. I can see it being a benefit for a media server more than an office file server. Byte and block level deduplication is preferred, but Windows Storage Server does not support that.

The performance hit associated is entirely dependent upon your environment. It's the proverbial "how long is a piece of string" question. There is no good answer to it. Use perfmon to see what the performance impacts are before and after SIS is enabled. If it's too intense, you can simply disable it. SIS is disabled on a volume rather easily.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.