I have 3 Windows 2008 R2 SP1 Servers (VM) and each one has svchost process that is taking up more than 1.2 GB of RAM. I understand that this is running RemoteRegistry Windows Service that could also be used for Performance Counters. I found this KB article that describes similar issues but only pertains to 2003 Server. I did check with server team and they are not running any Performance Counters.
Today an application (Informatica PowerCenter 9.0.1)
running on this server died twice and we finally restarted the entire server that been running for about 2 months. After restart svchost.exe -regsvc went down to about 5MB. In addition to that right before application crash I found the following events in Application log wmi performance adapter service entered the stopped state
not sure if this is related to Remote Registry service and somehow related to application crashing.
In next few month we are moving to Windows Server 2012 so I'm just trying to keep it running with minimal downtime until then.
Update: Screenshot below from Task Manager and from Process Explorer. Also a dialog box from Process Explorer showing the service. This is just from one of the three servers.
As you can see from the screenshot PID 1728 patches to ID in Process Explorer and inside Properties Window.
Edit:
These servers run Informatica 9.0.1 Power Center Server it is ETL tool build on Java (not a good start). Each machine runs 1 Windows Service that makes the whole application run. We have restarted windows service responsible for application multiple times including scheduled monthly maintenance, when service is shutdown and later brought back up few hours later. Since restart of OS RemoteRegistry service started at 3MB and so far grew to 10MB in 5hrs, 20MB in 12hrs. I will keep an eye to see when it starts growing out of proportion.
Also I found this KB Remote Registry service leaks memory when it handles customized v2 performance counter queries in Windows 7 or in Windows Server 2008 R2 http://support.microsoft.com/kb/2563399 and server OS is listed on list of effected OS. Not sure if it is related but I will check again to verify that no perfmon counters are being read. It could also be one of many monitoring applications that could be causing this.