Another small memory optimization that could be explored is getting rid of the runAllManagedModulesForAllRequest setting in the web.config (in the modules section).
Currently this is set to True, which means that every request (even for static content like images, CSS and JS files) gets handled by ASP.NET.
By removing the setting completely IIS will handle requests for static content outside of ASP.NET. This seems to work fine when I tested it, and reduces the overall memory usage somewhat (haven't had a chance to profile it properly).
Sure. Thanks a lot for suggestion. Done. Please see changeset 70947762ddef. Please give it a try. IMHO, looks much faster (haven't tested using Memory profiler yet)
P.S. Glad that VS developers also did it the default ASP.NET MVC template for VS 2013.
Currently this is set to True, which means that every request (even for static content like images, CSS and JS files) gets handled by ASP.NET.
By removing the setting completely IIS will handle requests for static content outside of ASP.NET. This seems to work fine when I tested it, and reduces the overall memory usage somewhat (haven't had a chance to profile it properly).
Sure. Thanks a lot for suggestion. Done. Please see changeset 70947762ddef. Please give it a try. IMHO, looks much faster (haven't tested using Memory profiler yet)
P.S. Glad that VS developers also did it the default ASP.NET MVC template for VS 2013.
I tried just changing the setting in web.config to false, and it caused some problems throughout my site. Admin menus wouldn't load, and customers couldn't add items to their cart...and probably other stuff too, but I switched it back to true as soon as I was aware.
I guess this isn't the proper procedure?
UPDATE:
Now I followed the link to codeplex and see other changes must be made...
Are the changes to the PageHeadBuilder.cs an absolute requirement?? (I use no source version)
I'm guessing this is what caused the admin menus not to load??
I became concerned about memory usage after upgrading to 3.30 and enabling some of the new performance features in configuration>>settings>> general and misc settings >> localization settings >>
I enabled Load all locale resources on startup, and Load all localized properties on startup, and the site does seem a bit more responsive.
I expected to take a memory usage hit by doing so, but it has pushed usage too high, and I'm looking now for other ways to lower my memory consumption without affecting page speed performance too adversely.
Prior to the upgrade, and enabling of the above mentioned settings, it was at about 650mb...creeping each day up to about 950mb
The w3wp.exe for my site, with approx 150 products...after fully loaded now uses about 1gb of RAM...creeping up to about 1.25gb each day. (leaks??)
Doesn't this seem a bit high?
Steve