Mariette Knap
Posts:102
| | 07/26/2006 5:14 AM |
| If you are using CuteSoft as your editor or you use ActiveForums and store zipped files in the database use these settings: < excludePaths>
<pathpattern="WebResource\.axd" />
<pathpattern="Install" />
<pathpattern="CuteSoft" />
<pathpattern="Chat" />
<pathpattern="Viewer\.aspx" />
excludePaths>The Chat exclusion prevents my super secret chat module to choke on loading Ajax :-) | |
 Mariette Knap - www.smallbizserver.net | |
|
|
|
John Mitchell
Posts:3248
| | 07/26/2006 5:26 AM |
| Excellent. Thanks for sharing I'm running a few more exclusions myself for Catalook mainly: < excludePaths>
<pathpattern="WebResource\.axd" />
<pathpattern="MakeThumbImage\.aspx" />
<pathpattern="590" />
<pathpattern="Download\.aspx" />
<pathpattern="Install" />
excludePaths>590 is my Cart tabid. | | | |
|
John Mitchell
Posts:3248
| | 07/26/2006 5:29 AM |
| Another tip. You don't need to comment out the module in web.config if you want to stop this module temporarily: Just put an exclude on all paths: < excludePaths>< pathpattern=".*" />excludePaths> The config file updates the module settings automatically without having to restart the app like a web.config change would do. | | | |
|
Mariette Knap
Posts:102
| | 07/26/2006 7:55 AM |
| Two more: < pathpattern="MailConnector" /> ActiveForums Mail connector
<pathpattern="Admin" /> I saw that admin pages are cached...don't like the idea :-) | |
Mariette Knap - www.smallbizserver.net | |
|
John Mitchell
Posts:3248
| | 07/26/2006 10:16 AM |
| One thing to keep in mind is that currently No pages are cached if a user is logged in. Only pages of request type "GET" and content type "text/html" are cached. Redirected pages are not cached. This module only caches pages for the anonymous user. The potential number of pages for identified users in most cases would give a diminishing rate of return. | | | |
|
Mariette Knap
Posts:102
| | 07/26/2006 10:42 AM |
| | Does this mean that caching on module level still makes sense? What are your plans for caching pages for authenticated users? | |
Mariette Knap - www.smallbizserver.net | |
|
John Mitchell
Posts:3248
| | 07/26/2006 10:53 AM |
| Excellent point. You're right, it would still be good to cache fairly static content at the module level so you get that advantage on logged in users.
When you do output caching of dynamic/personalized content though it is still very difficult and often not worth it if you have a lot of users and each page needs to be cached uniquely for them.
I'll probably start with the Administrators role when I attack the performance for logged in users, seeing as how this is the most painful area of performance. Caching by Role will probably yield good results overall.
I'm also going to add caching by using other specific parameters in the cookie to give some flexability there.
| | | |
|
John Mitchell
Posts:3248
| | 07/26/2006 11:32 AM |
| I was just checking my logs and ran across another one. the FreeTextBox pages used to insert images and smileys needs to be excluded. <pathpattern="ftb.*aspx" /> Let's see if I get a smiley: 
| | | |
|
Eric Swanzey
Posts:4
| | 07/26/2006 5:19 PM |
| sorry for my confusion, but doesn't blowery cache the logged in user's pages? When in a blowery site as an Admin, things seem to fly around pretty good. for pageBlaster, what's a good option to speed up the site for authenticated users? | | | |
|
John Mitchell
Posts:3248
| | 07/26/2006 5:46 PM |
| | Blowery only does compression, not caching. PageBlaster does the same thing Blowery does, including the authenticated users for compression, plus it does caching for anonymous users. | | | |
|
Dave Buckner
Posts:3
| | 07/26/2006 8:23 PM |
| err formatting got removed... path pattern=".*\.asmx" | | | |
|
John Mitchell
Posts:3248
| | 07/26/2006 10:14 PM |
| Thanks Dave.
Did you have a problem with a webservice being compressed? | | | |
|
Eric Swanzey
Posts:4
| | 07/26/2006 10:14 PM |
| Posted By Snapsis on 07/26/2006 5:46 PM
Blowery only does compression, not caching. PageBlaster does the same thing Blowery does, including the authenticated users for compression, plus it does caching for anonymous users. Excellent. Sign me up for the Pro version.
| | | |
|
Eric Swanzey
Posts:4
| | 07/26/2006 10:34 PM |
| try again, it disappeared above
add a path pattern for Orizonti_NukeNews | | | |
|
Dave Buckner
Posts:3
| | 07/26/2006 10:56 PM |
| Posted By Snapsis on 07/26/2006 10:14 PM
Thanks Dave.
Did you have a problem with a webservice being compressed?
Hi John,
No problem. Thank You!! Yes. I had issues with webservices being compressed. I can't say for sure this does/does not effect plain vanilla webservices though. The services I noticed this with only accept WSE SOAP Suds. From the error though it looks like maybe the handler is having a hard time finding the service cache file? The default was left for the cache path b.t.w. Could not find a part of the path "C:\Inetpub\wwwroot\DotNetNuke\DesktopModules\MyWebServices\portals\_default\Cache\". | | | |
|
Mariette Knap
Posts:102
| | 07/28/2006 3:42 AM |
| | In the Snapsis config file you need to add \ before the portals\_default\Cache\ | |
Mariette Knap - www.smallbizserver.net | |
|
John Mitchell
Posts:3248
| | 07/30/2006 4:59 PM |
| After reading all these excludes, and adding a lot of my own, I thought it would be good to look at this a little differently.
Each exclude has to be compared on each request so I wanted to limit them and combine some of the rules I had into one.
I thought about excluding everything except urls with default.aspx in it, which would get a lot and still cache everything, but that would leave my home page without being cached. So without further ado, here is a rule that will exclude all urls that have a ? (question mark) but do not have tabid in them.
pattern="\?(?!tabid)" />
Of course if there is a tabid that you still want to exclude, then you'll need to add that too, but those should be a lot less then all these external image resources, uploaders, downloaders, etc. | | | |
|
John Mitchell
Posts:3248
| | 07/31/2006 7:35 AM |
| Javascript and CSS files do not go through the ASP.Net pipeline so they are not compressed or cached on the server anyway. The good thing though is that those files are cached on the client on the first hit. Check out my blog about getting some extra bang on the first hit to the site for CSS in DotNetNuke.
http://blogs.snapsis.com/PermaLink,guid,2c5a4c45-bb33-4715-92be-578856d98661.aspx
| | | |
|
Mariette Knap
Posts:102
| | 07/31/2006 7:47 AM |
| | Thanks but makes it even more interesting to use native IIS compression because stylesheets and javascript gets compressed. Those files are only cached if you have set proper content expiration in IIS. Just open Fiddler and browse to www.dotnetnuke.com and you will see they did not setup any content expiration on IIS. I think this is one of the reasons that site is so slow.
Just an example what compression does:
spmenu: 67 kb not compressed, 15 kb compressed. If I look in my IIS Tempory Compressed Files folder I have a lot of stuff that gets compressed and cached. | |
Mariette Knap - www.smallbizserver.net | |
|
Mariette Knap
Posts:102
| | 07/31/2006 7:55 AM |
| | Oops... what happened? | |
Mariette Knap - www.smallbizserver.net | |
|