I compress mon IIS logs on a lot of IIS servers, albeit mainly servers that are hosting Outlook Web Access/App ou low volume web sites. J'ai no problems doing it, et assez like le disk space savings.
In general, you're trading CPU for storage by making this decision. If you're CPU-bound to begin avec alors this probably n'est pas a good tradeoff. For mon OWA servers, qui can grow gigabytes of logs a day (thanks ActiveSync devices) Je pense le tradeoff is a good one.
The NTFS filesystem driver handles le compression, so it ne change how IIS writes to le files.
Edit:
You are, potentially, aussi trading-off certains I/O bandwidth et IOPS, too. If you're a high enough volume that votre log writes are a significant consumption of I/O resources you could see a decline in I/O consumption depuis enabling compression, too.
The seulement way you're going to tell how this impacts you is to benchmark it yourself. Take a baseline avec compression disabled et alors enabled et compare them. Il y a no magic wand to wave to know how it will impact you-- il y a juste too beaucoup de non-deterministic factors in play.
