Hi Recently, they moved my production website and database on to virtual machines.
We experianced slow downs, timeouts on the website and blocking table locks on the database. The only thing was that each Morning, the first person to connect recalculates the cache for everyone else ( batch job before start of day ). Before the migration, the page took 22 seconds to load and pegged out all 8 cpu's on the db machine. After migration, it timed out after 15 min, using 2 cpu cores and 25% cpu capacity. The team that did the move took the average processor usage and set that as the max available cpu usage on the db and websites. It's fixed now. Davy "When all you have is a hammer, every problem looks like a nail." I feel much the same way about xml -----Original Message----- From: "Michael Lyons" <[email protected]> Sender: [email protected] Date: Mon, 30 May 2011 14:23:51 To: 'ozDotNet'<[email protected]> Reply-To: ozDotNet <[email protected]> Subject: RE: Website request slow performance / timeouts Noonie, No impersonation and connection pooling is on. Thanks for the suggestions was worth a double check. From: [email protected] [mailto:[email protected]] On Behalf Of noonie Sent: Thursday, 26 May 2011 10:39 PM To: ozDotNet Subject: Re: Website request slow performance / timeouts Michael, Just a long-shot... Are you impersonating the users when connecting to the database? Is connection pooling on? -- (mobile) noonie On 24/05/2011 2:29 PM, "Michael Lyons" <[email protected]> wrote: > I’ve been working on an ASP.Net solution which has a slow performance issues > and it has got me baffled. > > > > Problem: > > The production server randomly slows down when serving asp.net requests and > even times out. > > > > System architecture: > > The solution is hosted on a dedicated box which is running VmWares ESXi with > 4 VM servers sitting on it (1 per core). Each VM is on its own network. > > All network communication is done through a dedicated hardware firewall, > even between VM’s (unfortunately the auditor has to have it this way). > > Database is on 1 VM while another has the web server. > > ASP.Net is v4 running on IIS 7.5 while database is SQL Server 2008R2 all on > top of Windows Server 2008 R2 > > > > Analysis to date: > > I’ve run a profiler over the solution and so far come up with nothing that > really needs to be optimised. > > Our staging environment is running the same way as our production system > architecture minus the hardware firewall and has a lot lower hardware specs > but performs better than the production environment. When I’m talking > slower, I’m talking ¼ of the memory and a 7 year old CPU. > > Production IIS logs show some randomly high request execution times. > > > > Theories to date: > > ESXi is doing something weird and causing VM’s to run slow. > > Firewall is blocking requests randomly or is having performance issues, > although I don’t see it. > > IIS is randomly running slow. > > Sql Server is randomly running slow > > > > > > My questions: > > What would Windows performance counters would you watch? Besides the typical > CPU, Disk, memory and ASP.Net 4.0 counters? > > Does the IIS logs request execution times include the time to send the > network data? Eg. From time of socket open to time of socket closed? Or is > it just the pipeline without the TCP time included – eg. Serving a straight > html file would just really be time to read the file from disk. > > What else would you look at? > > > > > > ------ > > Michael Lyons >
