Windows Task Manager -- Sizes of Applications

[Guest Barry Karas]

17/Mar/2008 10:00

 

When I invoke the task manager it lists the applications that are running.

The applications sizes are not indicated. How would I get the size of each

application that is running to show?

 

Thank you,

 

Barry Karas

[Guest Avi Greenbury]

Re: Windows Task Manager -- Sizes of Applications

 

On Mon, 17 Mar 2008 10:19:26 -0400, Barry Karas wrote:

> 17/Mar/2008 10:00

>

> When I invoke the task manager it lists the applications that are

> running. The applications sizes are not indicated. How would I get the

> size of each application that is running to show?

>

 

What do you mean by 'size'?

 

It gives you the memory footprint, which is the only relevant 'size' I

can think of wanting.

If it's the size of the binary that you want (why?) the easiest way would

be to search for the executable in your $PATH. Could probably do a batch

file to do it, but given the apparent uselessness of the data I wouldn't

imagine it's already built in.

[Guest Barry Karas]

Re: Windows Task Manager -- Sizes of Applications

 

Size? In the PC world, size is usually measured in some form of byte.

 

Useless? Maybe to you?

 

Sincerely,

 

Barry Karas

-----------------------------------------------------------------------------------------------------------------------------------------

"Avi Greenbury" <avismailinglistaccount@googlemail.com> wrote in message

news:%238OcIIEiIHA.1204@TK2MSFTNGP03.phx.gbl...

> On Mon, 17 Mar 2008 10:19:26 -0400, Barry Karas wrote:

>

>> 17/Mar/2008 10:00

>>

>> When I invoke the task manager it lists the applications that are

>> running. The applications sizes are not indicated. How would I get the

>> size of each application that is running to show?

>>

>

> What do you mean by 'size'?

>

> It gives you the memory footprint, which is the only relevant 'size' I

> can think of wanting.

> If it's the size of the binary that you want (why?) the easiest way would

> be to search for the executable in your $PATH. Could probably do a batch

> file to do it, but given the apparent uselessness of the data I wouldn't

> imagine it's already built in.

[Guest Homer J. Simpson]

Re: Windows Task Manager -- Sizes of Applications

 

> Size? In the PC world, size is usually measured in some form of byte.

 

I don't think Avi was questioning what unit of measure you're after, but

rather, what it is you're trying to measure. Disk space utilization?

Memory footprint? Heap size?

> Useless? Maybe to you?

 

"Size" is useless without context. You need to define what you mean by

these "application sizes" figures you say aren't in Task Manager. Until you

do, we can only speculate.

 

In the meantime, start by going to Task Manager's Processes tab, then click

on View|Select Columns. There might be something you want in there. You

might also be interested in the performance counters (launch perfmon.msc),

or some of the data shown by Sysinternal's Process Explorer.

[Guest Bob I]

Re: Windows Task Manager -- Sizes of Applications

 

Look under Processes tab for that info.

 

Barry Karas wrote:

> Size? In the PC world, size is usually measured in some form of byte.

>

> Useless? Maybe to you?

>

> Sincerely,

>

> Barry Karas

> -----------------------------------------------------------------------------------------------------------------------------------------

> "Avi Greenbury" <avismailinglistaccount@googlemail.com> wrote in message

> news:%238OcIIEiIHA.1204@TK2MSFTNGP03.phx.gbl...

>

>>On Mon, 17 Mar 2008 10:19:26 -0400, Barry Karas wrote:

>>

>>

>>>17/Mar/2008 10:00

>>>

>>>When I invoke the task manager it lists the applications that are

>>>running. The applications sizes are not indicated. How would I get the

>>>size of each application that is running to show?

>>>

>>

>>What do you mean by 'size'?

>>

>>It gives you the memory footprint, which is the only relevant 'size' I

>>can think of wanting.

>>If it's the size of the binary that you want (why?) the easiest way would

>>be to search for the executable in your $PATH. Could probably do a batch

>>file to do it, but given the apparent uselessness of the data I wouldn't

>>imagine it's already built in.

>

>

>