Kevin K.
9 discussion posts
I used Sysinternals Process Monitor to monitor my system for ten seconds while not doing any window interaction at all. Much to my surprise, in that short amount of time DisplayFusion generated nearly 2,000 registry events. Is this normal? Are there any DisplayFusion features I can disable to reduce the number of registry operations?
(Win7 x64, DisplayFusion 3.4.1)
• Attachment [protected]: DisplayFusion-registry-events.zip [229,570 bytes]
Feb 10, 2012 (modified Feb 10, 2012)
•
#1
It is "normal" in that it's expected, but we're actually going to review this again and see if we can optimize it a bit :)
Thanks!
This should now be a bit better in DisplayFusion 3.5 Beta 7. There are still some registry checks and stuff that need to be done on a regular interval, but we've reduced the number or writes quite a bit.
Thanks!
Awesome, yeah, we've made a lot of performance improvements in the latest beta versions. Please let me know if you run into any more trouble :)
Thanks!
James Hood
1 discussion post
It's been three years since this thread was started, but I discovered this exact issue when checking Process Monitor yesterday with 7.1.
Could we please get some sort of commitment to try to clean this up?
DisplayFusion needs to use the registry to store and read session data quickly and reliably across different processes. Even though Process Monitor is showing the registry queries, once the data is read in from the registry, it's cached in memory for quicker access. Are you running into an issue that's caused by this?
