Thursday, March 03, 2005

I have been planning this blog for a long time. First, my background. I have been involved in IT for about six years, starting with VB5, moving through VB6 and ASP before working with Visual Studio .NET in late 2001. I've worked on some large enterprise solutions

http://www.microsoft.com/resources/casestudies/CaseStudy.asp?CaseStudyID=13677

and undertaken a lot of performance work on large databases

http://www.unisys.com/products/es7000__servers/hardware/index.htm

(largest server on MS platform at the time), and with .NET code. There have been numerous times over the past few years when I have really wanted to write down what I have been up to, so that when I'm working on something similar in the future, I have an easy reference.

After the initial flurry is over, I aim to post around once a week. This blog will concentrate on the MS platform, in particular .NET and SQL Server.

Cheers

Thursday, March 03, 2005 12:07:21 PM (GMT Standard Time, UTC+00:00)  #    Comments [6]  |  Trackback
Saturday, March 05, 2005 1:48:00 PM (GMT Standard Time, UTC+00:00)
How did you find the performance of the ES7000? Did you have any problems with the DS56525 cards over heating?
Tuesday, March 08, 2005 12:34:37 PM (GMT Standard Time, UTC+00:00)
We have problems with the DX56332 cards overheating, the engineer said it's because the fan speed is 6900 rpm instead of 7000 rpm. We had to put the machines in an extra cold room just to get rid of the problem as we were going through 2 cards a month and at $800 a card it was costing a fortune. Anyone else had this problem?
Tuesday, March 08, 2005 9:11:57 PM (GMT Standard Time, UTC+00:00)
You have to leave space between the DX56332 cards to stop them overheating

Use slots 1,3,5,7 and 9 or 2,4,6,8 and 10. This leaves enough ventalation space.
Wednesday, March 09, 2005 11:07:56 AM (GMT Standard Time, UTC+00:00)
Dave,

I can't say whether the ES7000 outperformed another server as we didn't benchmark against other machines - they were purchased before I joined the company. However, my view was that it only takes one stored proc with a problem to bring the machine to a crawl, and then it doesn't matter whether you have 2 or 32 processors.

One example I recall was that we were getting a lot of compile blocks

http://support.microsoft.com/default.aspx?scid=KB;en-us;q263889

which was causing all subsequent requests to queue up while the recompilation occured.

We used the KEEPFIXED PLAN

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql2k/html/sql_queryrecompilation.asp

to avoid compilation due to large inserts and deletes.
Note that we were happy to do this as the problems were occurring on permanent temporary tables (we got too much blocking using temp tables in tempdb) and the overall table size and index selectivity remained constant.
We also disabled parallelism, as with our short duration but high volume transactions, we felt this did not offer us any benefit.

We had one "issue" with the ES7000 but I'm not sure which component the problem was attributed to - I'll see if I can find out what it was.

Cheers Noel
Noel
Wednesday, March 09, 2005 5:37:35 PM (GMT Standard Time, UTC+00:00)
Dave,

We had problems with the "Oscar" system clock. Apparently in early ES7000's it was a single point of failure, and guess what!! I understand newer versions have a dual clock.

Cheers

Noel
Noel
Tuesday, March 15, 2005 5:35:27 PM (GMT Standard Time, UTC+00:00)
Noel,

We also had problems with our system clock, had to wind the damn thing up every morning otherwise is just stopped!

Mike
Mike
Comments are closed.

Theme design by Jelle Druyts

Pick a theme: