ProLiant DL380 G4 performance issues

[rpiddocke]

Hi,

This is a bit out there but I'm hoping to get any ideas I can to resolve my present issue. We are having serious performance issues on our new DL380 when using a custom WebService application on Windows 2003 Server.
The symptoms are that when the WebService is run a single processor peaks and the return times on the Service varies greatly. When we run the exact same Service on the same setup on an IBM Blade server, an older Compaq server or even my laptop (IBM T41), it runs fine with steady and reliable return times.
Calling the application directly (not via the WebService) or calling another generic WebService give fine results.

Does anyone have any experience or idea as to why a specific webservice would cause such behavior or can you point to what we should be looking at? What about this machine would cause this?

Thanks for any help whatsoever!

Robert

specs on machine:

ProLiant DL380 G4 R04 Xeon DP 3060-1.0MB/800 1P

ProLiant DL380 G4 Xeon DP 3060/1.0MB-800 Processor

Compaq 4GB (2 x 1GB) PC3200 DDR2 SDRAM DIMM Kit

146.8Gb 1" hpl Ultra320 10k (universal)

300Gb 1" hpl Ultra320 10k (universal)

Compaq Smart Array 5304 Cntrlr 256MB

specs on machine working fine:

IBM HS20 Blade Server:
2x. Intel Xeon DP 3,06GHz
4 GB RAM
2x. 36.4GB SCSI hard disks for the OS in RAID 1
1x. Fibrechannel Expansion
IBM BladeCenter:

IBM BladeCenter 8677-2XX
2x. IBM BladeCenter 4-port Gigabit Ethernet
2x. IBM BladeCenter 2-port Fibrechannel switch

[Steven E. Protter]

Shalom rpiddocke,

The serer is certainly fast enough for most appliations.

This could be a network misconfiguration isssue.

How are you measuring performance?

SEP

[rpiddocke]

Thanks for your reply.

After we started getting performance issues we moved the machine to our local rack from the hosting provider and are testing on the machine against the localhost. Our performance test is a custom application that hammers the web server with concurrent web service requests. On our IBM server we get steady replies of less than a second from the webservice. On the HP they start out below 1 second then jump to 4 and stay there for about 10 requests, then they jump to 20 seconds and down to 4 and up and down between 12 to 20 for the remainder of the test. Looking at the processors we can see one processor peaking at 100% for these requests. On other machines (including my laptop) the processor is not overly stressed.
We have tested another webservice calling a flat file, we have tested the target application that the webservice is connecting to so we believe that it is the webservice itself that is calling the application that is somehow disagreeing with the server. However, the webservice wrapper is very simple and completely standard.
Our next step is to either write or find another webservice to test which calls another application on the machine to see if this is a common behavior of webservices on this type of machine or a problem with our specific webservice and application combination.

Robert

[Ivan Ferreira]

You should use performance monitor to identify the problem. There are whell known counters that you need to monitor, see this article:

http://www.windowsnetworking.com/articles_tutorials/Key-Performance-Monitor-Counters.html

[rpiddocke]

Thanks.
Keep the suggestions coming please.

Specifically, Does anyone have any experience with poor performance using the .NET Framework 1.1 on these new servers; specifically when using it to communicate information from an application (dll) via the webservice with IIS?