Aucune remarque pour cette diapositive
On parlait des speakers, il y a une chose qui leur tient à cœur !
CPU READY : https://www.sqlskills.com/blogs/jonathan/cpu-ready-time-in-vmware-and-how-to-interpret-its-real-meaning/
Compilations : 10% des batch requests
Recompilations : 10% des compilations/ sec
Full scan : max 1/1000 du nombre de index searches
Forwarded records : 10% du nombre de batch requests
Pages split : 20% batch requests
The old recommendation was that PLE should have a minimum of about 300 seconds. This was from the days when SQL's BP was around 4GB or so. This therefore meant that for a read-mostly activity such as a report a PLE of 300 meant that the SAN was reading 4GB over 5 minutes, which calculates to about 3.4MB/s. These days we have BP's around the 64GB and above. So our 300 second threshold now means that the SAN would be reading about 218.5MB/s, which is a fair amount and likely to cause comment!
So what's a "good" PLE for a read-mostly operation like a report? Here's a handy formula I use to get a decent estimate:
PLE threshold = ((MAXBP(MB)/1024)/4)*300