About the only time dnn will take minutes to show a page is if the application pool is being recycled for some reason.  All asp.net sites suffer an intrinsic hit when the application pool is first started ... while the site structure is analysed and pre-compiled.

Im personally not a big fan of the webmartix installer process as it has some defaults that can cause issues - especially if its a win 7 operating system.

I do a lot of work while on the road and can have any number of dnn sites installed on my laptop. Never seen any performance issues apart from first page load time when I start a session - and then thats rarely more than 10 secs.

Things I would look at firstly - how much RAM do you have in your laptop ?  While the DNN/asp.net footprint is relatively small the MS SQL server foot print can push a memory starved computer into paging very quickly.

Secondly, what operating system are you running on ... different versions of windows and IIS have widely varying memory footprints.

Have you made any changes in the application pool - the most common cause of application pool refreshes is an application pool set to low memory usage or a low timeout. 

Oh and the most nasty culprit of all - what virus checker tool do you have installed on your laptop.  If its AVG or Norton's - these are two of the worst tools a website developer can have running on their system.  AVG can bring a website to a halt faster than a power outage and norton is not much better.

Westa

I've actually heard a bit of negative feedback about the WebMatrix installer causing some problems. I agree that simply setting up an simple site with the DNN Install package would be best. There is a small "startup" cost associated with ASP.Net for a site that is not currently active (which is easily addressed in production), but that should only be a matter of a couple seconds. I think the startup time you may be seeing now is startup time for some of the WebMatrix bits which are not required to run DNN.

---

Scott Willhite, Co-Founder DNN