Page faults in screensaver

[itcoordinator]

Sveiki,

We created a .scr file with only one image in it which is changing place every n seconds. The .scr is running on Windows 7 machines.
When hunting down performance issues in our (virtualized) environment, it was noticed that the screensaver is generating some 13-14 million page faults per hour - by far the highest of all processes that are running. This can be observed by using a program to open the task manager remotely (e.g. GoverLAN or psinfo).

Understandably part of our performance issues are thought to be at least related to the screensaver, also because the 'idle' desktops all show the company screensaver.

So the question is: can this be reproduced, and can it be fixed?

[Aivars]

We'll try to reproduce this problem. How much RAM do your virtualized environments have and how much of it is generally available?

[itcoordinator]

3.5 GB of which 80% is available.

Comparison:
- Screensaver Factory screensaver: running for 5 hours and 20 minutes, 77 million page faults and 246.109 seconds of CPU time.
- Antram Stardust Screen Saver Toolkit: running for 20 minutes, 2800 pagefaults. CPU usage: 0.031 seconds, memory: 6.3 MB

I am going to deploy the second one now since the performance benefit is substantial if you see this on 50 computers