You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-user@hadoop.apache.org by hadoop qi <ha...@gmail.com> on 2013/07/11 18:47:24 UTC
How are 'PHYSICAL_MEMORY_BYTES' and 'VIRTUAL_MEMORY_BYTES' calculated?
Hello,
I am wondering how memory counters 'PHYSICAL_MEMORY_BYTES' and
'VIRTUAL_MEMORY_BYTES' are calculated? They are peaks of memory usage or
cumulative usage?
Thanks for help,
Re: How are 'PHYSICAL_MEMORY_BYTES' and 'VIRTUAL_MEMORY_BYTES' calculated?
Posted by Vinod Kumar Vavilapalli <vi...@hortonworks.com>.
The snapshotting stops much before the actual JVM exits - when a map/reduce task is deemed done, the metric collection stops. The JVM exits a little later.
Thanks,
+Vinod
On Jul 12, 2013, at 3:57 PM, hadoop qi wrote:
> If a program terminates normally, i would assume its memory usage close to zero or at least very small, because the program release most memory it was allocated. That would mean all jobs in Hadoop had very small memory usage, because only the last point was measured. Actually, this is not case. We can see some programs with several G memory usage. Is that means at the end of the program it still hold several G memory? I am still confused.
>
> Regards,
> Qi
>
>
> On Fri, Jul 12, 2013 at 1:51 PM, Shahab Yunus <sh...@gmail.com> wrote:
> As Vinod Kumar Vavilapalli they are indeed snapshots in point and time. So they are neither the peak usage from the whole duration of the job, nor cumulative aggregate that increases over time.
>
> Regards,
> Shahab
>
>
> On Fri, Jul 12, 2013 at 4:47 PM, hadoop qi <ha...@gmail.com> wrote:
> Thanks for the response. So they represent the total physical memory (virtual memory) has been allocated to the job (e.g., from heap and stack) during its entire life time? I am still confused how to get the cumulative number from /proc/meminfo. I think from /proc/meminfo we can only get the memory usage of a process in a particular time point (looked like a snapshot of the status of the process). If these numbers are added, the sum would be much more than memory allocated to the program.
>
>
> On Fri, Jul 12, 2013 at 6:47 AM, Shahab Yunus <sh...@gmail.com> wrote:
> I think they are cumulative but per task.
>
> Physical memory bytes
> (PHYSICAL_MEMORY_BYTES)
> The physical memory being used by a task in bytes, as reported by /proc/meminfo.
> Virtual memory bytes
> (VIRTUAL_MEMORY_BYTES)
> The virtual memory being used by a task in bytes, as reported by /proc/meminfo.
>
> This is from the Definitive Guide book. Page 260.
>
> Regards,
> Shhab
>
>
> On Thu, Jul 11, 2013 at 12:47 PM, hadoop qi <ha...@gmail.com> wrote:
> Hello,
>
> I am wondering how memory counters 'PHYSICAL_MEMORY_BYTES' and 'VIRTUAL_MEMORY_BYTES' are calculated? They are peaks of memory usage or cumulative usage?
>
> Thanks for help,
>
>
>
>
Re: How are 'PHYSICAL_MEMORY_BYTES' and 'VIRTUAL_MEMORY_BYTES' calculated?
Posted by Vinod Kumar Vavilapalli <vi...@hortonworks.com>.
The snapshotting stops much before the actual JVM exits - when a map/reduce task is deemed done, the metric collection stops. The JVM exits a little later.
Thanks,
+Vinod
On Jul 12, 2013, at 3:57 PM, hadoop qi wrote:
> If a program terminates normally, i would assume its memory usage close to zero or at least very small, because the program release most memory it was allocated. That would mean all jobs in Hadoop had very small memory usage, because only the last point was measured. Actually, this is not case. We can see some programs with several G memory usage. Is that means at the end of the program it still hold several G memory? I am still confused.
>
> Regards,
> Qi
>
>
> On Fri, Jul 12, 2013 at 1:51 PM, Shahab Yunus <sh...@gmail.com> wrote:
> As Vinod Kumar Vavilapalli they are indeed snapshots in point and time. So they are neither the peak usage from the whole duration of the job, nor cumulative aggregate that increases over time.
>
> Regards,
> Shahab
>
>
> On Fri, Jul 12, 2013 at 4:47 PM, hadoop qi <ha...@gmail.com> wrote:
> Thanks for the response. So they represent the total physical memory (virtual memory) has been allocated to the job (e.g., from heap and stack) during its entire life time? I am still confused how to get the cumulative number from /proc/meminfo. I think from /proc/meminfo we can only get the memory usage of a process in a particular time point (looked like a snapshot of the status of the process). If these numbers are added, the sum would be much more than memory allocated to the program.
>
>
> On Fri, Jul 12, 2013 at 6:47 AM, Shahab Yunus <sh...@gmail.com> wrote:
> I think they are cumulative but per task.
>
> Physical memory bytes
> (PHYSICAL_MEMORY_BYTES)
> The physical memory being used by a task in bytes, as reported by /proc/meminfo.
> Virtual memory bytes
> (VIRTUAL_MEMORY_BYTES)
> The virtual memory being used by a task in bytes, as reported by /proc/meminfo.
>
> This is from the Definitive Guide book. Page 260.
>
> Regards,
> Shhab
>
>
> On Thu, Jul 11, 2013 at 12:47 PM, hadoop qi <ha...@gmail.com> wrote:
> Hello,
>
> I am wondering how memory counters 'PHYSICAL_MEMORY_BYTES' and 'VIRTUAL_MEMORY_BYTES' are calculated? They are peaks of memory usage or cumulative usage?
>
> Thanks for help,
>
>
>
>
Re: How are 'PHYSICAL_MEMORY_BYTES' and 'VIRTUAL_MEMORY_BYTES' calculated?
Posted by Vinod Kumar Vavilapalli <vi...@hortonworks.com>.
The snapshotting stops much before the actual JVM exits - when a map/reduce task is deemed done, the metric collection stops. The JVM exits a little later.
Thanks,
+Vinod
On Jul 12, 2013, at 3:57 PM, hadoop qi wrote:
> If a program terminates normally, i would assume its memory usage close to zero or at least very small, because the program release most memory it was allocated. That would mean all jobs in Hadoop had very small memory usage, because only the last point was measured. Actually, this is not case. We can see some programs with several G memory usage. Is that means at the end of the program it still hold several G memory? I am still confused.
>
> Regards,
> Qi
>
>
> On Fri, Jul 12, 2013 at 1:51 PM, Shahab Yunus <sh...@gmail.com> wrote:
> As Vinod Kumar Vavilapalli they are indeed snapshots in point and time. So they are neither the peak usage from the whole duration of the job, nor cumulative aggregate that increases over time.
>
> Regards,
> Shahab
>
>
> On Fri, Jul 12, 2013 at 4:47 PM, hadoop qi <ha...@gmail.com> wrote:
> Thanks for the response. So they represent the total physical memory (virtual memory) has been allocated to the job (e.g., from heap and stack) during its entire life time? I am still confused how to get the cumulative number from /proc/meminfo. I think from /proc/meminfo we can only get the memory usage of a process in a particular time point (looked like a snapshot of the status of the process). If these numbers are added, the sum would be much more than memory allocated to the program.
>
>
> On Fri, Jul 12, 2013 at 6:47 AM, Shahab Yunus <sh...@gmail.com> wrote:
> I think they are cumulative but per task.
>
> Physical memory bytes
> (PHYSICAL_MEMORY_BYTES)
> The physical memory being used by a task in bytes, as reported by /proc/meminfo.
> Virtual memory bytes
> (VIRTUAL_MEMORY_BYTES)
> The virtual memory being used by a task in bytes, as reported by /proc/meminfo.
>
> This is from the Definitive Guide book. Page 260.
>
> Regards,
> Shhab
>
>
> On Thu, Jul 11, 2013 at 12:47 PM, hadoop qi <ha...@gmail.com> wrote:
> Hello,
>
> I am wondering how memory counters 'PHYSICAL_MEMORY_BYTES' and 'VIRTUAL_MEMORY_BYTES' are calculated? They are peaks of memory usage or cumulative usage?
>
> Thanks for help,
>
>
>
>
Re: How are 'PHYSICAL_MEMORY_BYTES' and 'VIRTUAL_MEMORY_BYTES' calculated?
Posted by Vinod Kumar Vavilapalli <vi...@hortonworks.com>.
The snapshotting stops much before the actual JVM exits - when a map/reduce task is deemed done, the metric collection stops. The JVM exits a little later.
Thanks,
+Vinod
On Jul 12, 2013, at 3:57 PM, hadoop qi wrote:
> If a program terminates normally, i would assume its memory usage close to zero or at least very small, because the program release most memory it was allocated. That would mean all jobs in Hadoop had very small memory usage, because only the last point was measured. Actually, this is not case. We can see some programs with several G memory usage. Is that means at the end of the program it still hold several G memory? I am still confused.
>
> Regards,
> Qi
>
>
> On Fri, Jul 12, 2013 at 1:51 PM, Shahab Yunus <sh...@gmail.com> wrote:
> As Vinod Kumar Vavilapalli they are indeed snapshots in point and time. So they are neither the peak usage from the whole duration of the job, nor cumulative aggregate that increases over time.
>
> Regards,
> Shahab
>
>
> On Fri, Jul 12, 2013 at 4:47 PM, hadoop qi <ha...@gmail.com> wrote:
> Thanks for the response. So they represent the total physical memory (virtual memory) has been allocated to the job (e.g., from heap and stack) during its entire life time? I am still confused how to get the cumulative number from /proc/meminfo. I think from /proc/meminfo we can only get the memory usage of a process in a particular time point (looked like a snapshot of the status of the process). If these numbers are added, the sum would be much more than memory allocated to the program.
>
>
> On Fri, Jul 12, 2013 at 6:47 AM, Shahab Yunus <sh...@gmail.com> wrote:
> I think they are cumulative but per task.
>
> Physical memory bytes
> (PHYSICAL_MEMORY_BYTES)
> The physical memory being used by a task in bytes, as reported by /proc/meminfo.
> Virtual memory bytes
> (VIRTUAL_MEMORY_BYTES)
> The virtual memory being used by a task in bytes, as reported by /proc/meminfo.
>
> This is from the Definitive Guide book. Page 260.
>
> Regards,
> Shhab
>
>
> On Thu, Jul 11, 2013 at 12:47 PM, hadoop qi <ha...@gmail.com> wrote:
> Hello,
>
> I am wondering how memory counters 'PHYSICAL_MEMORY_BYTES' and 'VIRTUAL_MEMORY_BYTES' are calculated? They are peaks of memory usage or cumulative usage?
>
> Thanks for help,
>
>
>
>
Re: How are 'PHYSICAL_MEMORY_BYTES' and 'VIRTUAL_MEMORY_BYTES' calculated?
Posted by hadoop qi <ha...@gmail.com>.
If a program terminates normally, i would assume its memory usage close to
zero or at least very small, because the program release most memory it was
allocated. That would mean all jobs in Hadoop had very small memory usage,
because only the last point was measured. Actually, this is not case. We
can see some programs with several G memory usage. Is that means at the end
of the program it still hold several G memory? I am still confused.
Regards,
Qi
On Fri, Jul 12, 2013 at 1:51 PM, Shahab Yunus <sh...@gmail.com>wrote:
> As Vinod Kumar Vavilapalli they are indeed snapshots in point and time. So
> they are neither the peak usage from the whole duration of the job, nor
> cumulative aggregate that increases over time.
>
> Regards,
> Shahab
>
>
> On Fri, Jul 12, 2013 at 4:47 PM, hadoop qi <ha...@gmail.com> wrote:
>
>> Thanks for the response. So they represent the total physical memory
>> (virtual memory) has been allocated to the job (e.g., from heap and stack)
>> during its entire life time? I am still confused how to get the cumulative
>> number from /proc/meminfo. I think from /proc/meminfo we can only get the
>> memory usage of a process in a particular time point (looked like a
>> snapshot of the status of the process). If these numbers are added, the sum
>> would be much more than memory allocated to the program.
>>
>>
>> On Fri, Jul 12, 2013 at 6:47 AM, Shahab Yunus <sh...@gmail.com>wrote:
>>
>>> I think they are cumulative but per task.
>>>
>>> Physical memory bytes
>>> (PHYSICAL_MEMORY_BYTES)
>>> The physical memory being used by a task in bytes, as reported by
>>> /proc/meminfo.
>>> Virtual memory bytes
>>> (VIRTUAL_MEMORY_BYTES)
>>> The virtual memory being used by a task in bytes, as reported by
>>> /proc/meminfo.
>>>
>>> This is from the Definitive Guide book. Page 260.
>>>
>>> Regards,
>>> Shhab
>>>
>>>
>>> On Thu, Jul 11, 2013 at 12:47 PM, hadoop qi <ha...@gmail.com>wrote:
>>>
>>>> Hello,
>>>>
>>>> I am wondering how memory counters 'PHYSICAL_MEMORY_BYTES' and
>>>> 'VIRTUAL_MEMORY_BYTES' are calculated? They are peaks of memory usage or
>>>> cumulative usage?
>>>>
>>>> Thanks for help,
>>>>
>>>
>>>
>>
>
Re: How are 'PHYSICAL_MEMORY_BYTES' and 'VIRTUAL_MEMORY_BYTES' calculated?
Posted by hadoop qi <ha...@gmail.com>.
If a program terminates normally, i would assume its memory usage close to
zero or at least very small, because the program release most memory it was
allocated. That would mean all jobs in Hadoop had very small memory usage,
because only the last point was measured. Actually, this is not case. We
can see some programs with several G memory usage. Is that means at the end
of the program it still hold several G memory? I am still confused.
Regards,
Qi
On Fri, Jul 12, 2013 at 1:51 PM, Shahab Yunus <sh...@gmail.com>wrote:
> As Vinod Kumar Vavilapalli they are indeed snapshots in point and time. So
> they are neither the peak usage from the whole duration of the job, nor
> cumulative aggregate that increases over time.
>
> Regards,
> Shahab
>
>
> On Fri, Jul 12, 2013 at 4:47 PM, hadoop qi <ha...@gmail.com> wrote:
>
>> Thanks for the response. So they represent the total physical memory
>> (virtual memory) has been allocated to the job (e.g., from heap and stack)
>> during its entire life time? I am still confused how to get the cumulative
>> number from /proc/meminfo. I think from /proc/meminfo we can only get the
>> memory usage of a process in a particular time point (looked like a
>> snapshot of the status of the process). If these numbers are added, the sum
>> would be much more than memory allocated to the program.
>>
>>
>> On Fri, Jul 12, 2013 at 6:47 AM, Shahab Yunus <sh...@gmail.com>wrote:
>>
>>> I think they are cumulative but per task.
>>>
>>> Physical memory bytes
>>> (PHYSICAL_MEMORY_BYTES)
>>> The physical memory being used by a task in bytes, as reported by
>>> /proc/meminfo.
>>> Virtual memory bytes
>>> (VIRTUAL_MEMORY_BYTES)
>>> The virtual memory being used by a task in bytes, as reported by
>>> /proc/meminfo.
>>>
>>> This is from the Definitive Guide book. Page 260.
>>>
>>> Regards,
>>> Shhab
>>>
>>>
>>> On Thu, Jul 11, 2013 at 12:47 PM, hadoop qi <ha...@gmail.com>wrote:
>>>
>>>> Hello,
>>>>
>>>> I am wondering how memory counters 'PHYSICAL_MEMORY_BYTES' and
>>>> 'VIRTUAL_MEMORY_BYTES' are calculated? They are peaks of memory usage or
>>>> cumulative usage?
>>>>
>>>> Thanks for help,
>>>>
>>>
>>>
>>
>
Re: How are 'PHYSICAL_MEMORY_BYTES' and 'VIRTUAL_MEMORY_BYTES' calculated?
Posted by hadoop qi <ha...@gmail.com>.
If a program terminates normally, i would assume its memory usage close to
zero or at least very small, because the program release most memory it was
allocated. That would mean all jobs in Hadoop had very small memory usage,
because only the last point was measured. Actually, this is not case. We
can see some programs with several G memory usage. Is that means at the end
of the program it still hold several G memory? I am still confused.
Regards,
Qi
On Fri, Jul 12, 2013 at 1:51 PM, Shahab Yunus <sh...@gmail.com>wrote:
> As Vinod Kumar Vavilapalli they are indeed snapshots in point and time. So
> they are neither the peak usage from the whole duration of the job, nor
> cumulative aggregate that increases over time.
>
> Regards,
> Shahab
>
>
> On Fri, Jul 12, 2013 at 4:47 PM, hadoop qi <ha...@gmail.com> wrote:
>
>> Thanks for the response. So they represent the total physical memory
>> (virtual memory) has been allocated to the job (e.g., from heap and stack)
>> during its entire life time? I am still confused how to get the cumulative
>> number from /proc/meminfo. I think from /proc/meminfo we can only get the
>> memory usage of a process in a particular time point (looked like a
>> snapshot of the status of the process). If these numbers are added, the sum
>> would be much more than memory allocated to the program.
>>
>>
>> On Fri, Jul 12, 2013 at 6:47 AM, Shahab Yunus <sh...@gmail.com>wrote:
>>
>>> I think they are cumulative but per task.
>>>
>>> Physical memory bytes
>>> (PHYSICAL_MEMORY_BYTES)
>>> The physical memory being used by a task in bytes, as reported by
>>> /proc/meminfo.
>>> Virtual memory bytes
>>> (VIRTUAL_MEMORY_BYTES)
>>> The virtual memory being used by a task in bytes, as reported by
>>> /proc/meminfo.
>>>
>>> This is from the Definitive Guide book. Page 260.
>>>
>>> Regards,
>>> Shhab
>>>
>>>
>>> On Thu, Jul 11, 2013 at 12:47 PM, hadoop qi <ha...@gmail.com>wrote:
>>>
>>>> Hello,
>>>>
>>>> I am wondering how memory counters 'PHYSICAL_MEMORY_BYTES' and
>>>> 'VIRTUAL_MEMORY_BYTES' are calculated? They are peaks of memory usage or
>>>> cumulative usage?
>>>>
>>>> Thanks for help,
>>>>
>>>
>>>
>>
>
Re: How are 'PHYSICAL_MEMORY_BYTES' and 'VIRTUAL_MEMORY_BYTES' calculated?
Posted by hadoop qi <ha...@gmail.com>.
If a program terminates normally, i would assume its memory usage close to
zero or at least very small, because the program release most memory it was
allocated. That would mean all jobs in Hadoop had very small memory usage,
because only the last point was measured. Actually, this is not case. We
can see some programs with several G memory usage. Is that means at the end
of the program it still hold several G memory? I am still confused.
Regards,
Qi
On Fri, Jul 12, 2013 at 1:51 PM, Shahab Yunus <sh...@gmail.com>wrote:
> As Vinod Kumar Vavilapalli they are indeed snapshots in point and time. So
> they are neither the peak usage from the whole duration of the job, nor
> cumulative aggregate that increases over time.
>
> Regards,
> Shahab
>
>
> On Fri, Jul 12, 2013 at 4:47 PM, hadoop qi <ha...@gmail.com> wrote:
>
>> Thanks for the response. So they represent the total physical memory
>> (virtual memory) has been allocated to the job (e.g., from heap and stack)
>> during its entire life time? I am still confused how to get the cumulative
>> number from /proc/meminfo. I think from /proc/meminfo we can only get the
>> memory usage of a process in a particular time point (looked like a
>> snapshot of the status of the process). If these numbers are added, the sum
>> would be much more than memory allocated to the program.
>>
>>
>> On Fri, Jul 12, 2013 at 6:47 AM, Shahab Yunus <sh...@gmail.com>wrote:
>>
>>> I think they are cumulative but per task.
>>>
>>> Physical memory bytes
>>> (PHYSICAL_MEMORY_BYTES)
>>> The physical memory being used by a task in bytes, as reported by
>>> /proc/meminfo.
>>> Virtual memory bytes
>>> (VIRTUAL_MEMORY_BYTES)
>>> The virtual memory being used by a task in bytes, as reported by
>>> /proc/meminfo.
>>>
>>> This is from the Definitive Guide book. Page 260.
>>>
>>> Regards,
>>> Shhab
>>>
>>>
>>> On Thu, Jul 11, 2013 at 12:47 PM, hadoop qi <ha...@gmail.com>wrote:
>>>
>>>> Hello,
>>>>
>>>> I am wondering how memory counters 'PHYSICAL_MEMORY_BYTES' and
>>>> 'VIRTUAL_MEMORY_BYTES' are calculated? They are peaks of memory usage or
>>>> cumulative usage?
>>>>
>>>> Thanks for help,
>>>>
>>>
>>>
>>
>
Re: How are 'PHYSICAL_MEMORY_BYTES' and 'VIRTUAL_MEMORY_BYTES' calculated?
Posted by Shahab Yunus <sh...@gmail.com>.
As Vinod Kumar Vavilapalli they are indeed snapshots in point and time. So
they are neither the peak usage from the whole duration of the job, nor
cumulative aggregate that increases over time.
Regards,
Shahab
On Fri, Jul 12, 2013 at 4:47 PM, hadoop qi <ha...@gmail.com> wrote:
> Thanks for the response. So they represent the total physical memory
> (virtual memory) has been allocated to the job (e.g., from heap and stack)
> during its entire life time? I am still confused how to get the cumulative
> number from /proc/meminfo. I think from /proc/meminfo we can only get the
> memory usage of a process in a particular time point (looked like a
> snapshot of the status of the process). If these numbers are added, the sum
> would be much more than memory allocated to the program.
>
>
> On Fri, Jul 12, 2013 at 6:47 AM, Shahab Yunus <sh...@gmail.com>wrote:
>
>> I think they are cumulative but per task.
>>
>> Physical memory bytes
>> (PHYSICAL_MEMORY_BYTES)
>> The physical memory being used by a task in bytes, as reported by
>> /proc/meminfo.
>> Virtual memory bytes
>> (VIRTUAL_MEMORY_BYTES)
>> The virtual memory being used by a task in bytes, as reported by
>> /proc/meminfo.
>>
>> This is from the Definitive Guide book. Page 260.
>>
>> Regards,
>> Shhab
>>
>>
>> On Thu, Jul 11, 2013 at 12:47 PM, hadoop qi <ha...@gmail.com> wrote:
>>
>>> Hello,
>>>
>>> I am wondering how memory counters 'PHYSICAL_MEMORY_BYTES' and
>>> 'VIRTUAL_MEMORY_BYTES' are calculated? They are peaks of memory usage or
>>> cumulative usage?
>>>
>>> Thanks for help,
>>>
>>
>>
>
Re: How are 'PHYSICAL_MEMORY_BYTES' and 'VIRTUAL_MEMORY_BYTES' calculated?
Posted by Vinod Kumar Vavilapalli <vi...@hortonworks.com>.
No, every so often, 3 seconds IIRC, it capture pmem and vmem which corresponds to the usage of the process and its children at *that* specific point of time. Cumulative = cumulative across the process and its children.
Thanks,
+Vinod
On Jul 12, 2013, at 1:47 PM, hadoop qi wrote:
> Thanks for the response. So they represent the total physical memory (virtual memory) has been allocated to the job (e.g., from heap and stack) during its entire life time? I am still confused how to get the cumulative number from /proc/meminfo. I think from /proc/meminfo we can only get the memory usage of a process in a particular time point (looked like a snapshot of the status of the process). If these numbers are added, the sum would be much more than memory allocated to the program.
>
>
> On Fri, Jul 12, 2013 at 6:47 AM, Shahab Yunus <sh...@gmail.com> wrote:
> I think they are cumulative but per task.
>
> Physical memory bytes
> (PHYSICAL_MEMORY_BYTES)
> The physical memory being used by a task in bytes, as reported by /proc/meminfo.
> Virtual memory bytes
> (VIRTUAL_MEMORY_BYTES)
> The virtual memory being used by a task in bytes, as reported by /proc/meminfo.
>
> This is from the Definitive Guide book. Page 260.
>
> Regards,
> Shhab
>
>
> On Thu, Jul 11, 2013 at 12:47 PM, hadoop qi <ha...@gmail.com> wrote:
> Hello,
>
> I am wondering how memory counters 'PHYSICAL_MEMORY_BYTES' and 'VIRTUAL_MEMORY_BYTES' are calculated? They are peaks of memory usage or cumulative usage?
>
> Thanks for help,
>
>
Re: How are 'PHYSICAL_MEMORY_BYTES' and 'VIRTUAL_MEMORY_BYTES' calculated?
Posted by Shahab Yunus <sh...@gmail.com>.
As Vinod Kumar Vavilapalli they are indeed snapshots in point and time. So
they are neither the peak usage from the whole duration of the job, nor
cumulative aggregate that increases over time.
Regards,
Shahab
On Fri, Jul 12, 2013 at 4:47 PM, hadoop qi <ha...@gmail.com> wrote:
> Thanks for the response. So they represent the total physical memory
> (virtual memory) has been allocated to the job (e.g., from heap and stack)
> during its entire life time? I am still confused how to get the cumulative
> number from /proc/meminfo. I think from /proc/meminfo we can only get the
> memory usage of a process in a particular time point (looked like a
> snapshot of the status of the process). If these numbers are added, the sum
> would be much more than memory allocated to the program.
>
>
> On Fri, Jul 12, 2013 at 6:47 AM, Shahab Yunus <sh...@gmail.com>wrote:
>
>> I think they are cumulative but per task.
>>
>> Physical memory bytes
>> (PHYSICAL_MEMORY_BYTES)
>> The physical memory being used by a task in bytes, as reported by
>> /proc/meminfo.
>> Virtual memory bytes
>> (VIRTUAL_MEMORY_BYTES)
>> The virtual memory being used by a task in bytes, as reported by
>> /proc/meminfo.
>>
>> This is from the Definitive Guide book. Page 260.
>>
>> Regards,
>> Shhab
>>
>>
>> On Thu, Jul 11, 2013 at 12:47 PM, hadoop qi <ha...@gmail.com> wrote:
>>
>>> Hello,
>>>
>>> I am wondering how memory counters 'PHYSICAL_MEMORY_BYTES' and
>>> 'VIRTUAL_MEMORY_BYTES' are calculated? They are peaks of memory usage or
>>> cumulative usage?
>>>
>>> Thanks for help,
>>>
>>
>>
>
Re: How are 'PHYSICAL_MEMORY_BYTES' and 'VIRTUAL_MEMORY_BYTES' calculated?
Posted by Vinod Kumar Vavilapalli <vi...@hortonworks.com>.
No, every so often, 3 seconds IIRC, it capture pmem and vmem which corresponds to the usage of the process and its children at *that* specific point of time. Cumulative = cumulative across the process and its children.
Thanks,
+Vinod
On Jul 12, 2013, at 1:47 PM, hadoop qi wrote:
> Thanks for the response. So they represent the total physical memory (virtual memory) has been allocated to the job (e.g., from heap and stack) during its entire life time? I am still confused how to get the cumulative number from /proc/meminfo. I think from /proc/meminfo we can only get the memory usage of a process in a particular time point (looked like a snapshot of the status of the process). If these numbers are added, the sum would be much more than memory allocated to the program.
>
>
> On Fri, Jul 12, 2013 at 6:47 AM, Shahab Yunus <sh...@gmail.com> wrote:
> I think they are cumulative but per task.
>
> Physical memory bytes
> (PHYSICAL_MEMORY_BYTES)
> The physical memory being used by a task in bytes, as reported by /proc/meminfo.
> Virtual memory bytes
> (VIRTUAL_MEMORY_BYTES)
> The virtual memory being used by a task in bytes, as reported by /proc/meminfo.
>
> This is from the Definitive Guide book. Page 260.
>
> Regards,
> Shhab
>
>
> On Thu, Jul 11, 2013 at 12:47 PM, hadoop qi <ha...@gmail.com> wrote:
> Hello,
>
> I am wondering how memory counters 'PHYSICAL_MEMORY_BYTES' and 'VIRTUAL_MEMORY_BYTES' are calculated? They are peaks of memory usage or cumulative usage?
>
> Thanks for help,
>
>
Re: How are 'PHYSICAL_MEMORY_BYTES' and 'VIRTUAL_MEMORY_BYTES' calculated?
Posted by Vinod Kumar Vavilapalli <vi...@hortonworks.com>.
No, every so often, 3 seconds IIRC, it capture pmem and vmem which corresponds to the usage of the process and its children at *that* specific point of time. Cumulative = cumulative across the process and its children.
Thanks,
+Vinod
On Jul 12, 2013, at 1:47 PM, hadoop qi wrote:
> Thanks for the response. So they represent the total physical memory (virtual memory) has been allocated to the job (e.g., from heap and stack) during its entire life time? I am still confused how to get the cumulative number from /proc/meminfo. I think from /proc/meminfo we can only get the memory usage of a process in a particular time point (looked like a snapshot of the status of the process). If these numbers are added, the sum would be much more than memory allocated to the program.
>
>
> On Fri, Jul 12, 2013 at 6:47 AM, Shahab Yunus <sh...@gmail.com> wrote:
> I think they are cumulative but per task.
>
> Physical memory bytes
> (PHYSICAL_MEMORY_BYTES)
> The physical memory being used by a task in bytes, as reported by /proc/meminfo.
> Virtual memory bytes
> (VIRTUAL_MEMORY_BYTES)
> The virtual memory being used by a task in bytes, as reported by /proc/meminfo.
>
> This is from the Definitive Guide book. Page 260.
>
> Regards,
> Shhab
>
>
> On Thu, Jul 11, 2013 at 12:47 PM, hadoop qi <ha...@gmail.com> wrote:
> Hello,
>
> I am wondering how memory counters 'PHYSICAL_MEMORY_BYTES' and 'VIRTUAL_MEMORY_BYTES' are calculated? They are peaks of memory usage or cumulative usage?
>
> Thanks for help,
>
>
Re: How are 'PHYSICAL_MEMORY_BYTES' and 'VIRTUAL_MEMORY_BYTES' calculated?
Posted by Shahab Yunus <sh...@gmail.com>.
As Vinod Kumar Vavilapalli they are indeed snapshots in point and time. So
they are neither the peak usage from the whole duration of the job, nor
cumulative aggregate that increases over time.
Regards,
Shahab
On Fri, Jul 12, 2013 at 4:47 PM, hadoop qi <ha...@gmail.com> wrote:
> Thanks for the response. So they represent the total physical memory
> (virtual memory) has been allocated to the job (e.g., from heap and stack)
> during its entire life time? I am still confused how to get the cumulative
> number from /proc/meminfo. I think from /proc/meminfo we can only get the
> memory usage of a process in a particular time point (looked like a
> snapshot of the status of the process). If these numbers are added, the sum
> would be much more than memory allocated to the program.
>
>
> On Fri, Jul 12, 2013 at 6:47 AM, Shahab Yunus <sh...@gmail.com>wrote:
>
>> I think they are cumulative but per task.
>>
>> Physical memory bytes
>> (PHYSICAL_MEMORY_BYTES)
>> The physical memory being used by a task in bytes, as reported by
>> /proc/meminfo.
>> Virtual memory bytes
>> (VIRTUAL_MEMORY_BYTES)
>> The virtual memory being used by a task in bytes, as reported by
>> /proc/meminfo.
>>
>> This is from the Definitive Guide book. Page 260.
>>
>> Regards,
>> Shhab
>>
>>
>> On Thu, Jul 11, 2013 at 12:47 PM, hadoop qi <ha...@gmail.com> wrote:
>>
>>> Hello,
>>>
>>> I am wondering how memory counters 'PHYSICAL_MEMORY_BYTES' and
>>> 'VIRTUAL_MEMORY_BYTES' are calculated? They are peaks of memory usage or
>>> cumulative usage?
>>>
>>> Thanks for help,
>>>
>>
>>
>
Re: How are 'PHYSICAL_MEMORY_BYTES' and 'VIRTUAL_MEMORY_BYTES' calculated?
Posted by Vinod Kumar Vavilapalli <vi...@hortonworks.com>.
No, every so often, 3 seconds IIRC, it capture pmem and vmem which corresponds to the usage of the process and its children at *that* specific point of time. Cumulative = cumulative across the process and its children.
Thanks,
+Vinod
On Jul 12, 2013, at 1:47 PM, hadoop qi wrote:
> Thanks for the response. So they represent the total physical memory (virtual memory) has been allocated to the job (e.g., from heap and stack) during its entire life time? I am still confused how to get the cumulative number from /proc/meminfo. I think from /proc/meminfo we can only get the memory usage of a process in a particular time point (looked like a snapshot of the status of the process). If these numbers are added, the sum would be much more than memory allocated to the program.
>
>
> On Fri, Jul 12, 2013 at 6:47 AM, Shahab Yunus <sh...@gmail.com> wrote:
> I think they are cumulative but per task.
>
> Physical memory bytes
> (PHYSICAL_MEMORY_BYTES)
> The physical memory being used by a task in bytes, as reported by /proc/meminfo.
> Virtual memory bytes
> (VIRTUAL_MEMORY_BYTES)
> The virtual memory being used by a task in bytes, as reported by /proc/meminfo.
>
> This is from the Definitive Guide book. Page 260.
>
> Regards,
> Shhab
>
>
> On Thu, Jul 11, 2013 at 12:47 PM, hadoop qi <ha...@gmail.com> wrote:
> Hello,
>
> I am wondering how memory counters 'PHYSICAL_MEMORY_BYTES' and 'VIRTUAL_MEMORY_BYTES' are calculated? They are peaks of memory usage or cumulative usage?
>
> Thanks for help,
>
>
Re: How are 'PHYSICAL_MEMORY_BYTES' and 'VIRTUAL_MEMORY_BYTES' calculated?
Posted by Shahab Yunus <sh...@gmail.com>.
As Vinod Kumar Vavilapalli they are indeed snapshots in point and time. So
they are neither the peak usage from the whole duration of the job, nor
cumulative aggregate that increases over time.
Regards,
Shahab
On Fri, Jul 12, 2013 at 4:47 PM, hadoop qi <ha...@gmail.com> wrote:
> Thanks for the response. So they represent the total physical memory
> (virtual memory) has been allocated to the job (e.g., from heap and stack)
> during its entire life time? I am still confused how to get the cumulative
> number from /proc/meminfo. I think from /proc/meminfo we can only get the
> memory usage of a process in a particular time point (looked like a
> snapshot of the status of the process). If these numbers are added, the sum
> would be much more than memory allocated to the program.
>
>
> On Fri, Jul 12, 2013 at 6:47 AM, Shahab Yunus <sh...@gmail.com>wrote:
>
>> I think they are cumulative but per task.
>>
>> Physical memory bytes
>> (PHYSICAL_MEMORY_BYTES)
>> The physical memory being used by a task in bytes, as reported by
>> /proc/meminfo.
>> Virtual memory bytes
>> (VIRTUAL_MEMORY_BYTES)
>> The virtual memory being used by a task in bytes, as reported by
>> /proc/meminfo.
>>
>> This is from the Definitive Guide book. Page 260.
>>
>> Regards,
>> Shhab
>>
>>
>> On Thu, Jul 11, 2013 at 12:47 PM, hadoop qi <ha...@gmail.com> wrote:
>>
>>> Hello,
>>>
>>> I am wondering how memory counters 'PHYSICAL_MEMORY_BYTES' and
>>> 'VIRTUAL_MEMORY_BYTES' are calculated? They are peaks of memory usage or
>>> cumulative usage?
>>>
>>> Thanks for help,
>>>
>>
>>
>
Re: How are 'PHYSICAL_MEMORY_BYTES' and 'VIRTUAL_MEMORY_BYTES' calculated?
Posted by hadoop qi <ha...@gmail.com>.
Thanks for the response. So they represent the total physical memory
(virtual memory) has been allocated to the job (e.g., from heap and stack)
during its entire life time? I am still confused how to get the cumulative
number from /proc/meminfo. I think from /proc/meminfo we can only get the
memory usage of a process in a particular time point (looked like a
snapshot of the status of the process). If these numbers are added, the sum
would be much more than memory allocated to the program.
On Fri, Jul 12, 2013 at 6:47 AM, Shahab Yunus <sh...@gmail.com>wrote:
> I think they are cumulative but per task.
>
> Physical memory bytes
> (PHYSICAL_MEMORY_BYTES)
> The physical memory being used by a task in bytes, as reported by
> /proc/meminfo.
> Virtual memory bytes
> (VIRTUAL_MEMORY_BYTES)
> The virtual memory being used by a task in bytes, as reported by
> /proc/meminfo.
>
> This is from the Definitive Guide book. Page 260.
>
> Regards,
> Shhab
>
>
> On Thu, Jul 11, 2013 at 12:47 PM, hadoop qi <ha...@gmail.com> wrote:
>
>> Hello,
>>
>> I am wondering how memory counters 'PHYSICAL_MEMORY_BYTES' and
>> 'VIRTUAL_MEMORY_BYTES' are calculated? They are peaks of memory usage or
>> cumulative usage?
>>
>> Thanks for help,
>>
>
>
Re: How are 'PHYSICAL_MEMORY_BYTES' and 'VIRTUAL_MEMORY_BYTES' calculated?
Posted by hadoop qi <ha...@gmail.com>.
Thanks for the response. So they represent the total physical memory
(virtual memory) has been allocated to the job (e.g., from heap and stack)
during its entire life time? I am still confused how to get the cumulative
number from /proc/meminfo. I think from /proc/meminfo we can only get the
memory usage of a process in a particular time point (looked like a
snapshot of the status of the process). If these numbers are added, the sum
would be much more than memory allocated to the program.
On Fri, Jul 12, 2013 at 6:47 AM, Shahab Yunus <sh...@gmail.com>wrote:
> I think they are cumulative but per task.
>
> Physical memory bytes
> (PHYSICAL_MEMORY_BYTES)
> The physical memory being used by a task in bytes, as reported by
> /proc/meminfo.
> Virtual memory bytes
> (VIRTUAL_MEMORY_BYTES)
> The virtual memory being used by a task in bytes, as reported by
> /proc/meminfo.
>
> This is from the Definitive Guide book. Page 260.
>
> Regards,
> Shhab
>
>
> On Thu, Jul 11, 2013 at 12:47 PM, hadoop qi <ha...@gmail.com> wrote:
>
>> Hello,
>>
>> I am wondering how memory counters 'PHYSICAL_MEMORY_BYTES' and
>> 'VIRTUAL_MEMORY_BYTES' are calculated? They are peaks of memory usage or
>> cumulative usage?
>>
>> Thanks for help,
>>
>
>
Re: How are 'PHYSICAL_MEMORY_BYTES' and 'VIRTUAL_MEMORY_BYTES' calculated?
Posted by Vinod Kumar Vavilapalli <vi...@hortonworks.com>.
They are the running metrics. While the task is running, they will tell you how much pmem/vmem it is using at that point of time. Obviously at the end of job, it will be the last snapshot.
Thanks,
+Vinod
On Jul 12, 2013, at 6:47 AM, Shahab Yunus wrote:
> I think they are cumulative but per task.
>
> Physical memory bytes
> (PHYSICAL_MEMORY_BYTES)
> The physical memory being used by a task in bytes, as reported by /proc/meminfo.
> Virtual memory bytes
> (VIRTUAL_MEMORY_BYTES)
> The virtual memory being used by a task in bytes, as reported by /proc/meminfo.
>
> This is from the Definitive Guide book. Page 260.
>
> Regards,
> Shhab
>
>
> On Thu, Jul 11, 2013 at 12:47 PM, hadoop qi <ha...@gmail.com> wrote:
> Hello,
>
> I am wondering how memory counters 'PHYSICAL_MEMORY_BYTES' and 'VIRTUAL_MEMORY_BYTES' are calculated? They are peaks of memory usage or cumulative usage?
>
> Thanks for help,
>
Re: How are 'PHYSICAL_MEMORY_BYTES' and 'VIRTUAL_MEMORY_BYTES' calculated?
Posted by Vinod Kumar Vavilapalli <vi...@hortonworks.com>.
They are the running metrics. While the task is running, they will tell you how much pmem/vmem it is using at that point of time. Obviously at the end of job, it will be the last snapshot.
Thanks,
+Vinod
On Jul 12, 2013, at 6:47 AM, Shahab Yunus wrote:
> I think they are cumulative but per task.
>
> Physical memory bytes
> (PHYSICAL_MEMORY_BYTES)
> The physical memory being used by a task in bytes, as reported by /proc/meminfo.
> Virtual memory bytes
> (VIRTUAL_MEMORY_BYTES)
> The virtual memory being used by a task in bytes, as reported by /proc/meminfo.
>
> This is from the Definitive Guide book. Page 260.
>
> Regards,
> Shhab
>
>
> On Thu, Jul 11, 2013 at 12:47 PM, hadoop qi <ha...@gmail.com> wrote:
> Hello,
>
> I am wondering how memory counters 'PHYSICAL_MEMORY_BYTES' and 'VIRTUAL_MEMORY_BYTES' are calculated? They are peaks of memory usage or cumulative usage?
>
> Thanks for help,
>
Re: How are 'PHYSICAL_MEMORY_BYTES' and 'VIRTUAL_MEMORY_BYTES' calculated?
Posted by Vinod Kumar Vavilapalli <vi...@hortonworks.com>.
They are the running metrics. While the task is running, they will tell you how much pmem/vmem it is using at that point of time. Obviously at the end of job, it will be the last snapshot.
Thanks,
+Vinod
On Jul 12, 2013, at 6:47 AM, Shahab Yunus wrote:
> I think they are cumulative but per task.
>
> Physical memory bytes
> (PHYSICAL_MEMORY_BYTES)
> The physical memory being used by a task in bytes, as reported by /proc/meminfo.
> Virtual memory bytes
> (VIRTUAL_MEMORY_BYTES)
> The virtual memory being used by a task in bytes, as reported by /proc/meminfo.
>
> This is from the Definitive Guide book. Page 260.
>
> Regards,
> Shhab
>
>
> On Thu, Jul 11, 2013 at 12:47 PM, hadoop qi <ha...@gmail.com> wrote:
> Hello,
>
> I am wondering how memory counters 'PHYSICAL_MEMORY_BYTES' and 'VIRTUAL_MEMORY_BYTES' are calculated? They are peaks of memory usage or cumulative usage?
>
> Thanks for help,
>
Re: How are 'PHYSICAL_MEMORY_BYTES' and 'VIRTUAL_MEMORY_BYTES' calculated?
Posted by hadoop qi <ha...@gmail.com>.
Thanks for the response. So they represent the total physical memory
(virtual memory) has been allocated to the job (e.g., from heap and stack)
during its entire life time? I am still confused how to get the cumulative
number from /proc/meminfo. I think from /proc/meminfo we can only get the
memory usage of a process in a particular time point (looked like a
snapshot of the status of the process). If these numbers are added, the sum
would be much more than memory allocated to the program.
On Fri, Jul 12, 2013 at 6:47 AM, Shahab Yunus <sh...@gmail.com>wrote:
> I think they are cumulative but per task.
>
> Physical memory bytes
> (PHYSICAL_MEMORY_BYTES)
> The physical memory being used by a task in bytes, as reported by
> /proc/meminfo.
> Virtual memory bytes
> (VIRTUAL_MEMORY_BYTES)
> The virtual memory being used by a task in bytes, as reported by
> /proc/meminfo.
>
> This is from the Definitive Guide book. Page 260.
>
> Regards,
> Shhab
>
>
> On Thu, Jul 11, 2013 at 12:47 PM, hadoop qi <ha...@gmail.com> wrote:
>
>> Hello,
>>
>> I am wondering how memory counters 'PHYSICAL_MEMORY_BYTES' and
>> 'VIRTUAL_MEMORY_BYTES' are calculated? They are peaks of memory usage or
>> cumulative usage?
>>
>> Thanks for help,
>>
>
>
Re: How are 'PHYSICAL_MEMORY_BYTES' and 'VIRTUAL_MEMORY_BYTES' calculated?
Posted by hadoop qi <ha...@gmail.com>.
Thanks for the response. So they represent the total physical memory
(virtual memory) has been allocated to the job (e.g., from heap and stack)
during its entire life time? I am still confused how to get the cumulative
number from /proc/meminfo. I think from /proc/meminfo we can only get the
memory usage of a process in a particular time point (looked like a
snapshot of the status of the process). If these numbers are added, the sum
would be much more than memory allocated to the program.
On Fri, Jul 12, 2013 at 6:47 AM, Shahab Yunus <sh...@gmail.com>wrote:
> I think they are cumulative but per task.
>
> Physical memory bytes
> (PHYSICAL_MEMORY_BYTES)
> The physical memory being used by a task in bytes, as reported by
> /proc/meminfo.
> Virtual memory bytes
> (VIRTUAL_MEMORY_BYTES)
> The virtual memory being used by a task in bytes, as reported by
> /proc/meminfo.
>
> This is from the Definitive Guide book. Page 260.
>
> Regards,
> Shhab
>
>
> On Thu, Jul 11, 2013 at 12:47 PM, hadoop qi <ha...@gmail.com> wrote:
>
>> Hello,
>>
>> I am wondering how memory counters 'PHYSICAL_MEMORY_BYTES' and
>> 'VIRTUAL_MEMORY_BYTES' are calculated? They are peaks of memory usage or
>> cumulative usage?
>>
>> Thanks for help,
>>
>
>
Re: How are 'PHYSICAL_MEMORY_BYTES' and 'VIRTUAL_MEMORY_BYTES' calculated?
Posted by Vinod Kumar Vavilapalli <vi...@hortonworks.com>.
They are the running metrics. While the task is running, they will tell you how much pmem/vmem it is using at that point of time. Obviously at the end of job, it will be the last snapshot.
Thanks,
+Vinod
On Jul 12, 2013, at 6:47 AM, Shahab Yunus wrote:
> I think they are cumulative but per task.
>
> Physical memory bytes
> (PHYSICAL_MEMORY_BYTES)
> The physical memory being used by a task in bytes, as reported by /proc/meminfo.
> Virtual memory bytes
> (VIRTUAL_MEMORY_BYTES)
> The virtual memory being used by a task in bytes, as reported by /proc/meminfo.
>
> This is from the Definitive Guide book. Page 260.
>
> Regards,
> Shhab
>
>
> On Thu, Jul 11, 2013 at 12:47 PM, hadoop qi <ha...@gmail.com> wrote:
> Hello,
>
> I am wondering how memory counters 'PHYSICAL_MEMORY_BYTES' and 'VIRTUAL_MEMORY_BYTES' are calculated? They are peaks of memory usage or cumulative usage?
>
> Thanks for help,
>
Re: How are 'PHYSICAL_MEMORY_BYTES' and 'VIRTUAL_MEMORY_BYTES' calculated?
Posted by Shahab Yunus <sh...@gmail.com>.
I think they are cumulative but per task.
Physical memory bytes
(PHYSICAL_MEMORY_BYTES)
The physical memory being used by a task in bytes, as reported by
/proc/meminfo.
Virtual memory bytes
(VIRTUAL_MEMORY_BYTES)
The virtual memory being used by a task in bytes, as reported by
/proc/meminfo.
This is from the Definitive Guide book. Page 260.
Regards,
Shhab
On Thu, Jul 11, 2013 at 12:47 PM, hadoop qi <ha...@gmail.com> wrote:
> Hello,
>
> I am wondering how memory counters 'PHYSICAL_MEMORY_BYTES' and
> 'VIRTUAL_MEMORY_BYTES' are calculated? They are peaks of memory usage or
> cumulative usage?
>
> Thanks for help,
>
Re: How are 'PHYSICAL_MEMORY_BYTES' and 'VIRTUAL_MEMORY_BYTES' calculated?
Posted by Shahab Yunus <sh...@gmail.com>.
I think they are cumulative but per task.
Physical memory bytes
(PHYSICAL_MEMORY_BYTES)
The physical memory being used by a task in bytes, as reported by
/proc/meminfo.
Virtual memory bytes
(VIRTUAL_MEMORY_BYTES)
The virtual memory being used by a task in bytes, as reported by
/proc/meminfo.
This is from the Definitive Guide book. Page 260.
Regards,
Shhab
On Thu, Jul 11, 2013 at 12:47 PM, hadoop qi <ha...@gmail.com> wrote:
> Hello,
>
> I am wondering how memory counters 'PHYSICAL_MEMORY_BYTES' and
> 'VIRTUAL_MEMORY_BYTES' are calculated? They are peaks of memory usage or
> cumulative usage?
>
> Thanks for help,
>
Re: How are 'PHYSICAL_MEMORY_BYTES' and 'VIRTUAL_MEMORY_BYTES' calculated?
Posted by Shahab Yunus <sh...@gmail.com>.
I think they are cumulative but per task.
Physical memory bytes
(PHYSICAL_MEMORY_BYTES)
The physical memory being used by a task in bytes, as reported by
/proc/meminfo.
Virtual memory bytes
(VIRTUAL_MEMORY_BYTES)
The virtual memory being used by a task in bytes, as reported by
/proc/meminfo.
This is from the Definitive Guide book. Page 260.
Regards,
Shhab
On Thu, Jul 11, 2013 at 12:47 PM, hadoop qi <ha...@gmail.com> wrote:
> Hello,
>
> I am wondering how memory counters 'PHYSICAL_MEMORY_BYTES' and
> 'VIRTUAL_MEMORY_BYTES' are calculated? They are peaks of memory usage or
> cumulative usage?
>
> Thanks for help,
>
Re: How are 'PHYSICAL_MEMORY_BYTES' and 'VIRTUAL_MEMORY_BYTES' calculated?
Posted by Shahab Yunus <sh...@gmail.com>.
I think they are cumulative but per task.
Physical memory bytes
(PHYSICAL_MEMORY_BYTES)
The physical memory being used by a task in bytes, as reported by
/proc/meminfo.
Virtual memory bytes
(VIRTUAL_MEMORY_BYTES)
The virtual memory being used by a task in bytes, as reported by
/proc/meminfo.
This is from the Definitive Guide book. Page 260.
Regards,
Shhab
On Thu, Jul 11, 2013 at 12:47 PM, hadoop qi <ha...@gmail.com> wrote:
> Hello,
>
> I am wondering how memory counters 'PHYSICAL_MEMORY_BYTES' and
> 'VIRTUAL_MEMORY_BYTES' are calculated? They are peaks of memory usage or
> cumulative usage?
>
> Thanks for help,
>