PageBlaster 1.2 Released

This new version is even faster.  Here's a list of changes:

08/07/2006 v1.2
       -- Added the ability to limit the size of memory and disk space used.
          Config file              memory-size-limit:
                Set to to limit the size of the cache in memory (Megabytes)
             disk-size-limit:
                Set to to limit the size of the cache on disk (Megabytes)
        
       -- Optimized the speed for updating the cache .
      
       --Fixed a bug where the disk cache was being updated immediately
         after the page was pulled from disk.
      
       --Changed extension name of disk cache files to insure that other files were not
         deleted during the self-cleaning.  Cache folder should be cleaned manually
         after installing to make sure all old files are removed.

07/31/2006 v1.1
       -- Changed the place the filter is attached so that it would allow other filters
          to do thier work before compression was applied to the output.
     
       -- Added the ability to define the excludePaths with a more specific attribute
          called excludeFrom which can be set to "All", "Compression", or "Caching".
          This attribute can be added to your current excludePaths, but is not required.
          If it is not there it will default to "All".
         
       -- Updated the default config file with a new excludePath Rule that eliminates the need for
          most any other rules.  It automatically excudes all Urls with a Querystring that do not
          have a "tabid" parameter.  Change this to match your page-param if it is something other than tabid.
         
       -- Fixed a bug where the "none" setting on the compressionLevel was not actually
          disabling the compression.

A lot of webinfo files is not necessarily a bad thing.

Did you clear the cache of the files that end in just .webinfo? In this release I added a more unique extension to make sure that only PageBlaster cache files are deleted by the internal clean-up routine.

The new files will end with .pb.webinfo

Other than that, if you are concerned with disk space, then you can put a limit on the amount of disk space it uses in this new version also.

That is correct.  All needed instructions are in the readme.txt file, and the new attributes for memory-size-limit & disk-size-limit are not required unless you want to use them. 

They default to 10MB memory and 100MB disk if you don't set them, which is good for a small site, but most people will probably set it higher.

The higher the better, but i would probably leave it around 250MB memory and 500MB disk.

That's enough for ~10,000 pages in memory and twice that on disk (rough numbers based on ~25K per page).

No, this is a version that I am experimenting with the cache refreshing on.  I wanted to see if I could target in on the specific changes to highly active pages better so that I don't have to refresh all of them for a specific tab. These forums are a prime candidate, but there is a tradeoff that the updates may not show up on other Urls within the same page like in top posts, or the initial summary.

I'm still playing with it, but I kind of like to see when new posts are online right away, so I don't know if this is going to be worth it.

I also did some experimenting with viewstate and whitespace removal, but not a lot to gain there either on most pages.
Whitespace is negated with compression, removing HTML comments is another story though.

The pro version will have replacements capability, and should be ready early next week.