Hi Locopon,
thanks for your answer!
a) I use blowery for http compression.- For most new browsers, http compression is a MUST for everyone. You will have to check if all your modules work well with it. You can always exclude URL paths from compression
We recently enabled this. At first we had problems with HttpHandlers (Webresource.axd) that returned no data and caused many forms not to work, but after a little hack everything works fine. The effect is actually more than I imagined. I thought compression would increase CPU load and spare some bandwidth, but even the CPU load lowers drastically. Maybe the network device takes much of the CPU.
DSLocalizator can store that info inside your SQL server and avoid sending extra data to the final user.
Our database server has a strong usage by DNN and therefore a high CPU load. We believe that storing the viewstate there would make it worse.
Enable WhiteSpaceRemover.- DSLocalizator includes a feature that could remove your html spaces (Cr, tab, etc) to reduce the final response. The size of spaces from you page may depend of the kind of modules and content you have in your site.
We had this enabled for a short time. We should check this again...
In my opinion only massive caching can reduce CPU load. We noticed a lot of stored procedure calls by DSLocalizator. Is it a good idea to enable "Optimize with cache"?
We also noticed bad performance of some core stored procedures. E.g. hacking procedure GetTab resulted in a great performance boost.
Best regards,
Sebastian