2

I currently have Page Faults/sec avergaing 1269 while my Page Reads/sec is averaging 0.3.

I am just trying to interpret what this means. I assume I am getting lots of soft page faults in this case and the issue the user is experiencing with slowness is due to the application having to wait on pages to become free in memory?

In which case should I be tracking locking and blocking?

Improve this question

1 Answer 1

Reset to default
2

You are getting soft faults and this is a non-issue. Soft faults are part of the normal page lifetime as the process working set gets continuously trimmed.

If you also experience application problems then you need to investigate the cause. Read How to analyse SQL Server performance for a starting point.

Improve this answer
2
  • Thats a great link thanks. What do you think to tracking locks and blocks would this be the next logical step in troubleshooting the poor performance?
    – Tom
    Apr 24, 2015 at 10:40
  • 2
    Concurrency and performance are closely related. Blocking is often due to queries touching more data than needed for the task and performance is generally improved by touching the minimal amount of data. I suggest you first follow the Identifying Problem Queries section of the article. Ensure existing indexes are used as expected and predicates are sargable.
    – Dan Guzman
    Apr 24, 2015 at 12:13

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.