No...Way!! Garth Rules!

http://boxoffice.wynnlasvegas.com/shows_info.html

Worker Processes...Great question and answer.

http://stackoverflow.com/questions/2151251/asp-net-web-garden-how-many-worker-processes-do-i-need/2151390#2151390

 

What is the best practice for deciding how many worker processes to allow for an ASP.NET web application?

 

Worker processes are a way of segmenting the execution of your website across multiple exe's. You do this for a couple of reasons, one if one of the workers gets clobbered by run time issues it doesn't take the others down. For example, if a html request comes in that causes the process to run off into nothing then only the other requests that are being handled by that one worker processor get killed. Another example is that one request could cause blocking against the other threads handled by the same worker.

 

As far as how many you need, do some load testing. Hit the app hard and see what happens with only one. Then add some more to it and hit it again. At some point you'll reach a point of truly saturating the machines network, disk, cpu, and ram. That's when you know you have the right balance.

 

Incidentally, you can control the number of threads used per worker process via the machine.config file. I believe the key is maxWorkerThreads.

 

Now, beware, if you use session, Session state is not shared between worker processes. I generally recommend avoiding session anyway but it is something to consider.

 

For all intents and purposes you might consider each worker process as it's own separate web server. Except they are running on the same box.

 

 

Sensa - The new weight-loss system

Check this out.

 

This product has a guarantee that you’ll lose weight and offers a free trial so you can find out yourself…interesting!

 

http://www.howlifeworks.com/health_beauty/dietrevolution/?cid=8088pb_news_rm

 

Here’s a direct link to their site incase this article goes away: http://start.trysensa.com/dms1521/

 

I think I might want to try this. Lose weight for 5 bucks and no trying or counting calories, I like the sound of them apples.

 

Google Chrome on your Pages

So a while back I mentioned installing the Google Chrome engine for Internet Explorer to speed up page loads. HOWEVER…I failed to mention developing with the frame.

 

So here is the page that shows simple implementations to get your pages to load with the Google Chrome frame rather than IE even if you are using the IE browser.

 

http://code.google.com/chrome/chromeframe/developers_guide.html

 

Unfortunately, DotNetNuke skins are not all designed to work with this frame rendering god among men, so I can’t use it until I redesign my DNN skins…but rest-assured, I will implement this change as soon as I make my skins cross-browser compatible.