Hi John,

I did find Snapsis.PageBlaster.config file under my root folder, should I delete it? I think it specify the cache folder place. And the cache data seems save to

/Portals/_default/Cache/

folder.

I still have the error message said : Could not find a part of the path 'E:\inetpub\vhosts\sina101.com\httpdocs\portals\_default\Cache\LocalStrings\PageBlasterConfig.LocalStrings[zh-TW].js'.

I think it's the same reason.

I see something under /Portals/_default/Cache/  folder but I am not sure were them created by Page Blaster. It has some subfolder contains webinfo files.

Another question is about the license key, I see the license key when I download the community version. But I can't find a way to save it. I see a input box in the PageBlaster page but can't save it?

Did I need to config something for the community version?

And I have additional question about the profession version and community version. I am not sure what the real different. It look like community version will cache all data but profession version can let you "off" some feature. I don't know what the really benifit of the professional version.

Duchoangle:

I think that you, as well as Eric, have reached the wrong conclusion, with a bad methodology, based on bad information and wrong assumptions.  There are many factors involved in the performance of a Web site, to name a few, concurrent hits on the site, traffic on the line going to/from the site (may be shared with many other sites), Web server performance and workload, database server performance and workload, performance of a particular module, configuration parameters of the Web server and database server, design of the site, etc.  This site, the DNN site, have been having some problems related to its rapid growth, remember that this is a very high traffic site.  In particular, the Forums module have had some issues, which you see as slow performance of DNN, but it is not caused by the core of DNN necessarily, it is just that the forums is what people hit the most.

Also, you cannot compare the performance of a dynamic site like DNN with a plain, static, HTML page serving.  There is basically no effort on the server to send you a static HTML page.  If you can manage your site with plain HTML then by all means you should do it that way.  But if you need a more sophisticated site with all the functionality that DNN brings to the table then you are playing a different game in a different league.

And by the way, there is no C# version of DNN, where did you get that from???  And in any case, all the debates about the performance of C# versus VB.Net are irrelevant because both languages, as well as all the other languages supported by the .Net framework, compile to basically the same executable/binary code to be run by the Common Language Runtime or CLR, look it up.  Many fanatics of classic C and C++ get this confused all the time when they talk about C#, but neither C# or VB.Net generate native Windows binaries.

Yes, there is a delay when DNN starts if it has not been hit for a long period of time, this is a characteristic intrinsic to ASP.Net, not part of the design of DNN, but this has been discussed a lot and can be easily resolved.  Search for keepalive.

Also, regarding the use of Page Blaster, if you manage your own server you don't need it, you can setup compression at the IIS level and I consider that a better solution.  In any case you need a good, properly configured server for things to work smoothly.  I don't think the performance of DNN is something that you hear a lot of people complaining about, check your facts.

And Eric, your site is broken.

Carlos

Carlos,

Do you really think that doing compression with IIS is better than caching a dynamic page in memory and as a static file to persist app restarts?

Compression is good, but it doesn't do nearly as much for performance as page level caching.
With the new version of PageBlaster you even get automatic merging of CSS & JS files to reduce the number of http requests from one page which is increasingly becoming higher and higher with DNN.

Now, if compression is done once and the compressed page is cached (which PageBlaster does), then you can deliver the same cached page 1000's of times without taking the performance hit of what might be 100's of Database calls, Business logic, Page Rendering, and then compressing over and over again on every page request.

I'll agree that a good, and properly configured server can use brute force to overcome some of the performance problems that are the trade-off for having a dynamic site, but most people don't have the option of using a dedicated server and have to deal with the performance they can get from a overused shared server. 

The methodology Eric used is a good one.  Those facts on speed from Alexa are measured over long periods of time and are accurate as they relate from domain to domian.