VERY SLOW disk access - ml370 G1

[Alexander_61]

Hello there,

We have Win2k server ml370, 2 x 933Mhz , SmartArray 431 (RAID5 3 + 1 SPARE).
It works as Domain Controller in Active Directory + Exchange server. In regards of performance it is VERY, VERY slow. Especially in comparrison to standard member servers. File access speed is just probably 5-6 times slower.
Microsoft support have checked network monitor traffic statistics and didn't find any problem, it was, like "DC is more loaded than any other server".
Performance monitor statistics is fine, no bottlenecks... Any ideas how to improve the speed?
BTW, SMB signing is already off.

[Rune J. Winje]

Hi,
I think we need some more info regarding your setup.

This is the WS2003 forum.

Is the server a Windows 2000 server or 2003.

Perfmon -> Physical disk -> Avb. Disk Queue lenght
Is this >2 ? If so disk system will need redesign.

Other questions: Exchange - what version? (5.5 possibly uses port 389 which is the same the AD (LDAP) uses)

Disk layout?
Windows pagefile.sys location?
Exchange database and log file locations?
Exchange AD connector?
Any error messages in the event logs?


Cheers,
Rune

[Rune J. Winje]

Hi,
one additional question.

Is DNS also setup on this server?
(If so ipconfig /all )

Cheers,
Rune

[Alexander_61]

Sorry,
It is Windows 2000, I should have picked up another topic.
Anyway,
Maximum disk queue length (Average ~ 0.19), maximum 1.4
Exchange = 2000
Disks = 3 x 18.2 Ultra2 SCSI in RAID5 0n 431 controller + 1 Spare
Logically - 2 disks, C: and D: both NTFS
pagefile.sys is on D: (numbers are in picture attached)
Exchange database files are on D:, Logs are on C:
No any error messages in Event log.
DNS is set up on that server as a part of AD install.
IPCONFIG /ALL:
Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : server1
Primary DNS Suffix . . . . . . . : domain.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : domain.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : domain.com
Description . . . . . . . . . . . : HP NC3163 Fast Ethernet NIC
Physical Address. . . . . . . . . : 00-50-8B-DE-7C-29
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.11
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.254
DNS Servers . . . . . . . . . . . : 192.168.1.11
Primary WINS Server . . . . . . . : 192.168.1.11

Thanks,
Alexander

[Rune J. Winje]

The disk activity looks OK since max is 1.4 and average 0.19

The disk setup could be more optimal, but the numbers don't seem to indicate a real problem. (However check that write-back caching is enabled on the RAID controller, write-through caching is often x6 the write time).

DNS address on network card looks OK (points to itself).

I see that domain.com is officially registered as a domain-name. If you own it, fine, if not choose another to avoid DNS problems. Both AD and Exchange depend on DNS and quick replies from DNS.

Try NSLOOKUP to troubleshoot DNS response. (Use ipconfig /flushdns first so cached DNS-lookups do not fool you) Also check that forwarders-tab in DNS is not greyed out and that the monitor tab gives sub-second response to both simple and recursive tests (otherwise there _is_ a DNS problem)

Running AD + Exchange + DNS + WINS +... on one server is not recommended. Also separate disks for system, pagefile, database files and log-files are recommended.

What does task-manager show regarding CPU-graphs and available RAM?

Processes - View - Select Columns - VM Size, Threads, Page Faults, PF Delta
(Increase in Threads count over time could indicate "leaky" app)


Cheers,
Rune

[Gert_5]

We have about a same situation, just except the system is a ML370 G2 machine. Since yesterday we have the same problem. Did you finally find a resolution for this case?

We now replaced the Compaq NC3163 driver with the Microsoft driver. Since the reboot the performance now is okay, I hope this keeps on working fine.

[Keith Purpura_1]

Exchange 5.5 on a Domain Controller is not a good idea.
Because AD LDAP is on port 389 change the exchange 5.5 port to 390.
If you want any perfomance to the RAID I would suggest using all 6 drives in a RAID 5 configration. I have this same server in my house and I noticed that a 3 disk array was unusable on this machine as fars as disk acces was concerned.I would suggest using 6 Ultra 160 15000 RPM drives in a RAID 5 to achieve maximum performance.
I have noticed that the internal NIC on the server sometimes needs some tweaking on the recevice threshold.
You have alot of stuff running on that server so it may be advisable to think about migrating the exchange server off the DC. The exchange database can grow rapidly and the transaction logs are very intensive on the server as well. Contiguous space is the exchange 5.5 server database friend and a good formula to follow is 1 1/2 times free disk space of actual database size on the exchange drive. This allows for offline compaction and is a good rule of thumb to follow. In addition SP4 is mandatory for EXH 5.5. I wouldnt put SP4 on WIN 2000 Just yet unless you are running it as a WEB Server for ASP.NET

Other solutions are Memory Memory Memory.

Also try the latest driver set from compaq.
I have been very happy with 6.40 and have not gone to a higher numbered driver set.

I hope this helps

KP