CodeGuru Home VC++ / MFC / C++ .NET / C# Visual Basic VB Forums Developer.com
Results 1 to 2 of 2

Thread: looking for source of major page faults

  1. #1
    Join Date
    May 2009

    looking for source of major page faults


    I am working on a tool that is running alright but /usr/bin/time -v indicates 1393 major page faults. This doesn't make any sense because the footprint of the application is only 356608 kb and I have ~2.5GB of available RAM. Why would the system be paging the application unless it doesn't have all the RAM it needs?

    I am not sure how to track this down? Should I profile the app first? Would that tell me where in the code this is happening?


  2. #2
    Join Date
    Feb 2017

    Re: looking for source of major page faults

    It may not necessarily have to do with page swapping.

    It may be that your tool is loading utilities from disc (possibly at start) and that the benchmark program is counting this as major page faults.
    Last edited by wolle; August 11th, 2018 at 02:29 AM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

Windows Mobile Development Center

Click Here to Expand Forum to Full Width

On-Demand Webinars (sponsored)