Date: Thu, 28 Mar 2024 19:04:04 +0000 (UTC) Message-ID: <1087870089.68859.1711652644396@ip-10-0-1-26.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_68858_269342506.1711652644392" ------=_Part_68858_269342506.1711652644392 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This metric counts the number of =
physical database writes the disk sub-system performs. This value is measur=
ed by reading PAGE READS/SEC
from sysperfinfo
.
Currently, even the fastest disks can sup= port a maximum sustained rate of around only 85 random IOs per second. To d= etermine if your IO subsystem is "flooded," perform the following calculati= on:
((Page reads + read ahead pages + ((page writes + chec=
kpoint pages + lazy writes + log flushes) X 4)) / number of disk spindles i=
n RAID array)
must be < 65. ((Page reads + read ahead pages + ((page writes + che=
ckpoint pages + lazy writes + log flushes) X 2)) / number of disk spindles =
in RAID array)
must be < 65.If the page writes rate exceeds 65 for mo= re than five seconds every 20 minutes, then consider the following:
DBCC DLLNAME (FREE). Once an extended stored procedure is called, it remains in memory unt=
il SQL Server is shut down even if it is never called again! This is tremen=
dously wasteful in terms of available memory and a DBCC DLLNAME (FREE=
)
releases that memory for use by both the procedure cache as well a=
s the Data Pages which has a significant positive effect on both the Proced=
ure Cache Hit Ratio as well as the Buffer Cache Hit Ratio. In order to view=
the extended stored procedures currently loaded in memory by SQL Server, e=
xecute SP_HELPEXTENDEDPROC
.