wyclef1
asked on
RPC Latency per database
Hi
I see in Exchange 2007/Windows 2008 Server Perfmon there is a counter for RPC Average Latency, but this seems to be per server.
Is there any way to drill this down to per database/storage group?
I assume that if the databases are held on seperate LUN's, then high RPC Latency for one DB wouldn't cause an increase in RPC Latency on another? Or would it?
I see in Exchange 2007/Windows 2008 Server Perfmon there is a counter for RPC Average Latency, but this seems to be per server.
Is there any way to drill this down to per database/storage group?
I assume that if the databases are held on seperate LUN's, then high RPC Latency for one DB wouldn't cause an increase in RPC Latency on another? Or would it?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
If your latency issues are caused by poor disk performance it should only affect the database on the poor performing disks.
JJ
JJ
Does this apply to you?
From: http://technet.microsoft.com/en-us/library/aa998266(EXCHG.80).aspx
RPC Averaged Latency
The RPC Averaged Latency performance counter records the average time, in milliseconds (ms), that it takes for the last 1024 packets to be processed. The latency represents how long it takes from the time the Store.exe process received the packet to the time it returned the packet. The RPC Averaged Latency performance counter does not include any network latency or any latency that is introduced by anything other than the Store.exe process. Although the RPC Averaged Latency performance counter data does not include network transit time, it does provide data about the shortest time period that client computers have waited for a response from the server. If the RPC Averaged Latency performance counter data is lower than 50 ms, the server can process the requests in a reasonable amount of time. If the counter stays greater than 50 ms for more than several seconds, this indicates that the server is having difficulty keeping up with the load. As a result, users may experience delays when accessing their e-mail. If average latency is greater than 100 ms, users will receive the following pop-up window from their Microsoft Office Outlook® client computers: "Retrieving data from Exchange Server."
From: http://technet.microsoft.com/en-us/library/aa998266(EXCHG.80).aspx
RPC Averaged Latency
The RPC Averaged Latency performance counter records the average time, in milliseconds (ms), that it takes for the last 1024 packets to be processed. The latency represents how long it takes from the time the Store.exe process received the packet to the time it returned the packet. The RPC Averaged Latency performance counter does not include any network latency or any latency that is introduced by anything other than the Store.exe process. Although the RPC Averaged Latency performance counter data does not include network transit time, it does provide data about the shortest time period that client computers have waited for a response from the server. If the RPC Averaged Latency performance counter data is lower than 50 ms, the server can process the requests in a reasonable amount of time. If the counter stays greater than 50 ms for more than several seconds, this indicates that the server is having difficulty keeping up with the load. As a result, users may experience delays when accessing their e-mail. If average latency is greater than 100 ms, users will receive the following pop-up window from their Microsoft Office Outlook® client computers: "Retrieving data from Exchange Server."
ASKER
So does this mean that high latency on one DB can affect users on another? Even if they are on seperate LUN's?