As you can assume, a developer running the server configuration for a site like this can be hectic from times. Each month this site continues to grow in members, readers, and content, so some failure was going to happen with the default settings of IIS. Through the month of January we started receiving Deadlocks and "Server Too Busy" errors on the site and it was becoming unstable. Is started debugging and researching the issue, finding most results saying, "throw more servers at it!". Well I really didn't want to jump on the multiple web server track yet because the memory and processors are not being tacked.
So I reached out to Chris Haaker, our resident IT Hero, and asked him for some advice. Quickly after my email, he opened a thread with me and pointed me to this article. It covers how to configuration IIS and ASP.net to maximize server performance. After some alterations, the server started up and is performing like it was a year ago with half the traffic. If you are hosting a site and don't want to face issues like these, I highly suggest reading this article now.
Thanks Chris!