Archive for June 11th, 2006

11 Jun 2006

How to identify an IT consultant?

No Comments Fun & Humorous

Once upon a time there was a shepherd looking after his sheep on the side of a deserted road. Suddenly a brand new Porsche screeches to a halt. The driver, a man dressed in an Armani suit, Cerutti shoes, Ray-Ban sunglasses, TAG-Heuer wrist-watch, and a Pierre Cardin tie, gets out and asks the shepherd: “If I can tell you how many sheep you have, will you give me one of them?” The shepherd looks at the young man, and then looks at the large flock of grazing sheep and replies: “Okay.” The young man parks the car, connects his laptop to the mobile-fax, enters a NASA Webster, scans the ground using his GPS, opens a database and 60 Excel tables filled with logarithms and pivot tables, then prints out a 150 page report on his high-tech mini-printer. He turns to the shepherd and says, “You have exactly 1,586 sheep here.” The shepherd cheers, “That’s correct, you can have your sheep.”

The young man makes his pick and puts it in the back of his Porsche. The shepherd looks at him and asks: “If I guess your profession, will you return my animal to me?” The young man answers, “Yes, why not?” The shepherd says, “You are an IT consultant.” “How did you know?” asks the young man. “Very simple,” answers the shepherd. “First, you came here without being called. Second, you charged me a fee to tell me something I already knew, and third, you don’t understand anything about my business…Now can I have my DOG back?”

11 Jun 2006

ASP.NET 2.0, 1 Database Server, 1 IIS 6.0 Web Server and 32,000 Concurrent Connections!

No Comments ASP.NET

Markus Frind has posted his experience of using ASP.NET 2.0 for one of largest dating site PlentyOfFish.com in Canada. In his post, Markus is telling how he has addressed concurrency issues by switching to ASP.NET 2.0:

At this point there were a lot of concurrency issues, the site would slooow down and just keep getting slower as more people came on. After switching to asp.net 2.0 all those problems went away. Now when there are over 32,000 concurrent connections at peak the site does not slow down. There are however still problems. I find that once you pass 100 Pageviews/second threads timers start to not get called for no reason.

URL : Microsoft ASP.NET 2.0 Performance

Interestingly, he didn’t use any kind of caching to render pages. Every page hit actually pull content from database.

Great Post!