Even though I like the Beerhouse a lot, I have not been impressed by its responsetime.
I found a tool to analyse the display of web pages by showing each requested item on the page, how big it is, if it was cached and how long it takes to retrieve it. See www.ieinspector.com
- IE HTTP Analyzer.
Just clicking on the home page, about and contact pages repeatedly did not seem as quick as one would expect with cached content.
I tried a few known installations of the BeerHouse, like www.dotnet2themax.com/thebeerhouse
All of these sites had four instances of the file WebResource.axd totalling of over 70kb that would be loaded everytime and did not get cached. The pages never loaded instantly like pages with most of the content cached should do and all had some time with a blank browser window between the page displays.
It turns out that in debug builds these references don't get cached. When it put up the BeerHouse on my own test server and built it with debug=false in web.config, the .axd files would get cached as one would expect. And the pages would display much quicker without the annoying blanking in-between.
So I can only assume that the websites mentioned earlier are built with the debug version of the BeerHouse.
One more thing, the traces from the analyser showed that in addition to the page requested, there was a request for the Default.aspx page.
For example when I clicked on the Contact page on www.ericengler.com
the tracer would show 12 references, mostly gifs, css files etc. Request 1 was for http://www.ericengler.com/Contact.aspx
, request 2 was for http://www.ericengler.com/
which is the Default.aspx page 36922 bytes. All other pages would also get this page. I have noticed this behavior also on ASP.NET sites not built with the BeerHouse but I don't know the reason for this request. It does not get cached for some reason.