Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
heda_p
Starting Member
5 Posts |
Posted - 2002-07-13 : 00:46:02
|
| Configuration:two sanbox each has 6 read/write heads( having 10 raid array of each consisting 6 disks).database 500 GB * 1 on second sanbox.tempdb datafiles 30 GB * 2 on first sanbox on raid 0+1.database logfiles 40 GB * 1 on second sanbox raid 0+1.tempdb logfiles 20 GB * 1 on second sanbox raid 0+1.After this our processes are getting slowed then before Earlier tempdb data and log file + database log file on one raid 0+1 and this was working better.At that time we had only first sanbox, second is added this time only.I suspect this could be because of network because of adding new sanbox.sysprocesses table always shows networkio as last waittype, this message is saying that somthing is wrong on network but here communication is between server and the two sanboxes only. These sanboxes are connected through fiber channels. Performance monitor shows lot of activity in ms tcp loopback interface while other three ethernet cards are not having much activityHere the experts look into this problem as per them network could not be the issue but they don't know what is ms tcp loopback interface and why is showing hell lot of activity.I beleave this ms tcp loopback interface has somthing to do with this problem any ideas what is this and how it work?????All other things are same and this server is configured in the context to deliver best performance.PrakashCheers,Prakash |
|
|
jasper_smith
SQL Server MVP & SQLTeam MVY
846 Posts |
Posted - 2002-07-13 : 11:31:31
|
| The MS loopback adapter is something you can install on a standalone server to "imitate" network connectivity. For example you cannot install Active Directory on a standalone server with no network card so ehat happens if you wnat to have a test server not on the network - install the Loopback adapter and away you go. I have no idea why it would be installed on your server but mayve its something to do with your SAN config - I wouldn't really know. I tsounds very much like SQL is getting blocked on network IO and that would be the area to conecentrate on but thes configurations tend to be very specific to an individual site/server so your tech guys and the SAN vendor are probably your best hope.HTHJasper Smith |
 |
|
|
|
|
|