[EMAIL PROTECTED] / 05.1.30 / 00:11 AM wrote:
Remember that VSize is the amount of address space that has been allocated to a process. It is not the amount of Virtual Memory that the process is actually using. You now have more memory in your machine...so it really isn't strange that you have more address space being allocated. There are memory management algorithms that figure all of this out but I don't know enough about them to say exactly how they work.
The definition of VSIZE in Linux: VSIZE (Virtual memory SIZE) - The amount of memory the process is currently using. This includes the amount in RAM and the amount in swap.
I'm not really familiar with the way Linux Systems deal with memory. So VSize in Linux may mean something different than VSize in OS X. (as you know, OS X is Unix based...VM in OS X is a decendent of Mach VM)
Besides VSize always matches with vm allocation that Activity Monitor shows for a running app.
Yes...VSize matches with vm allocation because it is the same thing...the key word here is "allocation" which is different than "current usage." Think of it as "I'm going to allocate an hour tomorrow morning to run errands" I have assigned myself (much as the OS assigns virtual memory to a process or app.... which is what VSize represents in OS X) a specific amount of time to do these errands...I may not use the whole time but this is what I have have set aside based on what I think will be needed.
I am confused :-(
Here...:-)
<http://www.osxfaq.com/dailytips/03-2002/03-18.ws>
-K
-- _______________________________________________ Finale mailing list [email protected] http://lists.shsu.edu/mailman/listinfo/finale
