|}
Ideally, As one should always can see from the table, compression can greatly reduce the amount of data to transfer. So theoretically, it is recommended to turn it on and use a higher compression level 9whenever possible. HoweverIn practice, if though, one has to check the server following facts before making such a decision.* CPU : Compression will require additional CPU processing power (more for higher levels).* Network bandwidth: The lower the bandwidth, the more sense it makes to enable compression.In the table above, one might already notice the reduction in time is not powerful enough linear to the reduction in data amount. Take level 0 and level 9 for example, the time is already struggling "only" cut in half even when the data amount is reduced by 85%. These were tested with heavy load without compression, one can use some lower compression levela 54Mbps bandwidth. In Once we did our tests again with a lot of cases450Mbps bandwidth, level 4 offers the time reduction is even less (less than 6 minutes v.s. 3 minutes). If the bandwidth increases further, e.g. to Gbps, the time reduction might become negligible. Combined with a good leverageweak CPU, it is even possible that the time is increased with higher compression levels.Therefore, there is no general rulebooks for whether to turn on compression or not. The safest approach is still to try out different settings in the real setup.
As for the memory consumption, no observable difference was found between different compression settings (no compression and level 0 to 9) during our testing.
[[Category:How-To|Configure Microsoft IIS for UBIK]][[Category:Installing|Configure Microsoft IIS for UBIK]][[Category:Pages with broken file links|Configure Microsoft IIS for UBIK]][[Category:Web service|Configure Microsoft IIS for UBIK]]
== Create new Web Application ==
