I have been getting occasional issues with the ehttpsrv.exe processing going haywire and eating up a full core of cpu cycles out of nowhere. Everything appears to be functioning fine, but console response crawls and client updates a slowed due to CPU contention. Restarting the RA service or even forcing a manual update on the mirror seems to resolve the issue for a few hours, but it eventually comes back. Are other people seeing these same symptoms? On a side note, while I was picking through the activity on the ehttpsrv process trying to figure out what was going on, I noticed that it is constantly hitting disk to read the update.ver and mod_compat.mod files in the mirror. Why aren't these files kept loaded in memory with the process if they see so much I/O?