A user asked for help on a high pagefault issue with the process "Micorosft.mashup.container.netFX45.exe" in PowerBI. Another user shared that page faults can occur due to memory being paged out or opening large files. It is important to check memory utilization, interaction with stored files, and user experience indicators. A specific user’s issue was discussed and it was found that the page file was not significantly used.
Read the entire ‘Troubleshooting High Pagefault Numbers in ControlUp Community’ thread below:
Hi all! I heard from a ControlUp user today that they were seeing high pagefault numbers for the “Micorosft.mashup.container.netFX45.exe” process (PowerBI), and they wanted to know what causes that and what to do about it. I’m wondering if anyone here in the Community has had a similar challenge in the past, and better yet – if anyone has a recommended solution!?
Page faults are kind of a soft metric to diagnose. As in, CPU is pretty easy to diagnose. High CPU is (almost always) bad. Page faults are a bit more abstract.
A page fault could happen because the operating system paged memory out to the paging file and it needs to read that memory back into physical memory.
Or it could happen because I just tried to open a giant file in Excel.
The first one might be a problem because reading from disk (page file) is slow and could impact user experience. The 2nd one is completely normal.
Yet both will appear as page faults.
Generally speaking:
• Check memory utilization of the system, is it high? Then the operating system is more likely to page memory to the page file. Though as far as I’m aware, this is largely decided by the operating system. So it isn’t exact science.
• Does the application interact with stored files?
• Does it pre-load files or does it access files only when it needs them?
• Are there indicators of user experience issues? Primarily user input delay.
Thank you, Dennis!!
Hi Dennis — appreciate your feedback. The user is performing a transformation in PowerBI with a set of data (about 115 rows and 10-12 columns). It takes a non-persistent VDI about 15-20 seconds to finish, and a persistent VDI half of that time. When I check the resource utilization of the NP VDI, it shows about 80-85% memory utilization at the highest while the CPU isn’t stressed. There is significant disk read and write operations while this in progress and that is when we see the 30000-40000 page faults.
The page file on the VDI is 10GB and not being significantly used.
Continue reading and comment on the thread ‘Troubleshooting High Pagefault Numbers in ControlUp Community’. Not a member? Join Here!
Categories: All Archives, ControlUp for VDI