Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Heavy waits on PAGEIOLATCH_SH got cleared after restarting web application Expand / Collapse
Author
Message
Posted Wednesday, January 9, 2013 3:07 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Wednesday, December 3, 2014 11:49 AM
Points: 231, Visits: 723
Hi,

I noticed unusually heavy waits on PAGEIOLATCH_SH during an UPDATE activity and it was taking few hours.

Below error is noticed in SQL Server error log.

SQL Server has encountered 42443 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [H:\data\***.mdf] in database [****(5). The OS file handle is 0x00000000000007D4. The offset of the latest long I/O is: 0x000009cd260000

Surprisingly after restarting the web application, UPDATEs went fine without any issue. It was a Java based web application hosted in web logic and uses connection pooling to connect to SQL Server database.

Did anyone found similar issues any time? It is tricky that application restart has cleared the waits on PAGEIOLATCH_SH.

Thanks.
Post #1404638
Posted Thursday, January 10, 2013 11:37 PM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Wednesday, December 3, 2014 11:49 AM
Points: 231, Visits: 723
One more observation is that below error is logged only after restarting the web logic application. Before restarting the application service, UPDATE was stuck on I/O, getting processed very slowly but no error is logged in SQL Server error log.

SQL Server has encountered 42443 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [H:\data\***.mdf] in database [****(5). The OS file handle is 0x00000000000007D4. The offset of the latest long I/O is: 0x000009cd260000

After restarting the application, same query ran fine without any I/O latency issue.

Did anyone observe similar problem any time?

Thanks.
Post #1405777
Posted Friday, January 11, 2013 12:47 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: 2 days ago @ 2:16 AM
Points: 2,840, Visits: 3,983
PAGEIOLATCH_SH means slowness in IO operations. this is the one cent which will come to anyone's mind who will look into your posts.its might be happening because BIg tables invole in this UPDATE and NOT using the indexes efficienty .

Can you post the query long with the exec plan ?


-------Bhuvnesh----------
I work only to learn Sql Server...though my company pays me for getting their stuff done
Post #1405788
Posted Friday, January 11, 2013 12:48 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: 2 days ago @ 2:16 AM
Points: 2,840, Visits: 3,983
see this link too http://blog.sqlauthority.com/2011/02/09/sql-server-pageiolatch_dt-pageiolatch_ex-pageiolatch_kp-pageiolatch_sh-pageiolatch_up-wait-type-day-9-of-28/

-------Bhuvnesh----------
I work only to learn Sql Server...though my company pays me for getting their stuff done
Post #1405790
Posted Friday, January 11, 2013 2:13 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Wednesday, December 3, 2014 11:49 AM
Points: 231, Visits: 723
One thing that I don't understand is error got logged only after restarting the web application and then when same UPDATE query was run, it ran fine without waiting on I/O.

Could outdated statistics be the reason behind I/O latency?

Thanks.
Post #1405833
Posted Friday, January 11, 2013 3:23 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: 2 days ago @ 2:16 AM
Points: 2,840, Visits: 3,983
praveen_vejandla (1/11/2013)
Could outdated statistics be the reason behind I/O latency?

it might be . there could be another reason too like memory , IO , table/index scan happening. Please post the exec plan so that we can dig out further


-------Bhuvnesh----------
I work only to learn Sql Server...though my company pays me for getting their stuff done
Post #1405857
Posted Friday, January 11, 2013 5:03 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 8:51 PM
Points: 7,140, Visits: 12,763
42443 occurrence(s) of I/O requests taking longer than 15 seconds to complete



praveen_vejandla (1/11/2013)
One thing that I don't understand is error got logged only after restarting the web application and then when same UPDATE query was run, it ran fine without waiting on I/O.

[quote]Could outdated statistics be the reason behind I/O latency?

Thanks.

It looks like your disk subsystem is having frequent problems keeping up with the workload being thrown at it. Outdated statistics are not necessarily a cause of that but they can contribute to the problem. If some statistics are out of date and the query optimizer is using sub-optimal execution plans because of them then the database engine may be working harder than it should have to in order to retrieve results to satisfy a query. When is the last time you ran index and stats maintenance routines on your databases? Adding index and stats maintenance to an already overloaded system needs to be done carefully.

I would also recommend you check the disk subsystem for overall health including running CHECKDB on your databases (PS which also need to be done at a time chosen carefully on an already overloaded system).


__________________________________________________________________________________________________
There are no special teachers of virtue, because virtue is taught by the whole community. --Plato
Post #1405914
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse