How to see memory usage on windows xp

Peter Lawrey Peter Lawrey k 73 73 gold badges silver badges bronze badges. Jason Brennecke Jason Brennecke 61 1 1 silver badge 4 4 bronze badges. Lucas Araujo 1, 12 12 silver badges 23 23 bronze badges. Joshua Love Joshua Love 49 3 3 bronze badges. Perhaps better changing the string to just "Memory" viz. This will only give you back five entries, all connected with memory — noonand. Arshed Arshed 2 2 silver badges 11 11 bronze badges. Try MemLog. It does the job perfectly and quickly.

OperatingSystemMXBean java. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Stack Gives Back Safety in numbers: crowdsourcing data on nefarious IP addresses. Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually.

Linked 1. Related Hot Network Questions. Question feed. Note this is similar to Finegrained performance reporting on svchost. There is an easy way to get the information you are asking for but it does require a slight change to your system :. Do this in a command line window or put it into a BAT script. Administrative privileges are required and a restart of the computer is required before it takes effect. This technique has no ill effects, except perhaps increasing memory consumption slightly.

EXE process that has a lot of services. I have used this sequence it can be pasted directly into a command line window :. Services aren't necessarily hosted by svchost. It will show all services. Now you can view and sort on the memory usage of individual services implemented by dlls within the svchost. While Process Monitor is a general purpose utility that will do everything but wash dishes for you , for this particular question you want to use VMMap another SysInternals utility.

VMMap is a process virtual and physical memory analysis utility. It shows a breakdown of a process's committed virtual memory types as well as the amount of physical memory working set assigned by the operating system to those types.

Besides graphical representations of memory usage, VMMap also shows summary information and a detailed process memory map. Powerful filtering and refresh capabilities allow you to identify the sources of process memory usage and the memory cost of application features.

Besides flexible views for analyzing live processes, VMMap supports the export of data in multiple forms, including a native format that preserves all the information so that you can load back in.

It also includes command-line options that enable scripting scenarios. This is getting into stackoverflow territory, but if you can get hold of per-thread memory stats you may be able to roughly correlate that to the individual service dlls by matching them up to the dlls listed in the thread stack. Way too much for my tiny sysadmin brain, though. I extend Peter Mortensen's answer here. Before modifying the type of services, please check the existing type by command like:.

Separating the services is the correct answer, but the sc config command didn't work for me R2. You can do it via the registry though, which means setting the "Type" parameter to 0x dec. Be careful though which service you choose to modify, there are special types besides "own" and "share" that shouldn't be changed, like:.

After that, just restart the service and you should see in ProcessExplorer that it now has its own svchost. Sign up to join this community. At this point, your Memory Tracker will look like the one shown in Figure. If you wish to extend the monitoring operation to a longer time period, you can set the time interval to seconds. Doing so will set the Duration to exactly one hour. Next, click the Clear Display button on the Memory Tracker toolbar to get a clean slate and then minimize the window.

Now, use the computer as you normally would, making sure that you really put the system to work performing all the types of tasks that you do on a normal workday.

When the minute time period is up, maximize your Memory Tracker window and immediately click the Freeze Display button on the toolbar. Instead, you really need to take a close look at each individual counter.

Rather the goal is to aggregate the data provided by each counter in order to obtain the full picture. To assist you in your analysis, click the Highlight button on the toolbar. Doing so will highlight the appropriate line on the graph when you select the counter in the legend. This counter shows you the amount of physical memory that is available to any processes running on the computer during the time period.

By looking at the values in the Minimum and Maximum boxes you can see how the amount of physical memory fluctuated in relation to the other items. In an optimal situation, the values in both the Average and Minimum boxes should be more than 4MB.

This counter indicates the number of pages being read from or written to virtual memory in order to resolve accesses to data that was not in physical memory at the time of the reference.

In an optimal situation, the values in both the Average and Maximum boxes should be less than The counters in the Server category deal directly with the amount of and use of physical memory. In an optimal situation, the values of both these counters should be 0. Any values above 0 indicate that the system needs more memory.

Now, the Pool Nonpaged Peak counter indicates the maximum size, in bytes, of the nonpaged pool that the system had in use at any one point.

The value of this counter is a key figure in evaluating memory because it indicates how much physical memory the computer should have for optimal performance. Values between 50 and 75 are pretty standard fare. However, if the value approaches , this could indicate either of two situations: First, the size of the paging file is simply too small. Since the act of paging data from physical to virtual memory involves writing and reading to the hard disk, keeping an eye on the physical disk for increased activity can also help confirm the need for more memory.