pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Check Pointer
9+ messages / 7 participants
[nested] [flat]

* Check Pointer
@ 2013-05-30 12:09 itishree sukla <itishree.sukla@gmail.com>
  2013-05-30 12:20 ` Re: Check Pointer Greg Smith <greg@2ndQuadrant.com>
  2013-05-30 12:20 ` Re: Check Pointer Dinesh Kumar <dinesh.kumar@enterprisedb.com>
  2013-05-30 12:26 ` Re: Check Pointer Heikki Linnakangas <hlinnakangas@vmware.com>
  0 siblings, 3 replies; 9+ messages in thread

From: itishree sukla @ 2013-05-30 12:09 UTC (permalink / raw)
  To: pgsql-performance

Hi all,

In our server Check pointer process is consuming 8 GB of memory, what could
be the possible reason? Can any one please help.

Regards,
Itishree

^ permalink  raw  reply  [nested|flat] 9+ messages in thread

* Re: Check Pointer
  2013-05-30 12:09 Check Pointer itishree sukla <itishree.sukla@gmail.com>
@ 2013-05-30 12:20 ` Greg Smith <greg@2ndQuadrant.com>
  2 siblings, 0 replies; 9+ messages in thread

From: Greg Smith @ 2013-05-30 12:20 UTC (permalink / raw)
  To: pgsql-performance; itishree.sukla@gmail.com

On 5/30/13 8:09 AM, itishree sukla wrote:
> In our server Check pointer process is consuming 8 GB of memory, what
> could be the possible reason? Can any one please help.

That process will eventually access all of shared_buffers, which shows 
as a shared memory block for that process.  That's what you're seeing 
there.  It doesn't actually use any significant amount of memory on its own.

-- 
Greg Smith   2ndQuadrant US    greg@2ndQuadrant.com   Baltimore, MD
PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.com


-- 
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance



^ permalink  raw  reply  [nested|flat] 9+ messages in thread

* Re: Check Pointer
  2013-05-30 12:09 Check Pointer itishree sukla <itishree.sukla@gmail.com>
@ 2013-05-30 12:20 ` Dinesh Kumar <dinesh.kumar@enterprisedb.com>
  2 siblings, 0 replies; 9+ messages in thread

From: Dinesh Kumar @ 2013-05-30 12:20 UTC (permalink / raw)
  To: itishree sukla <itishree.sukla@gmail.com>; +Cc: pgsql-performance

Hi ,

Could you share the command, what you have used to confirm that, the
checkpoint process is consuming 8GB. And also, please share the addition
information like PostgreSQL version and the OS details.

I am suspecting that, your shared_buffers value is 8GB, and the "top"
command is showing the used memory as 8GB.

Thanks.

Dinesh

-- 
*Dinesh Kumar*
Software Engineer

Ph: +918087463317
Skype ID: dinesh.kumar432
www.enterprisedb.co
<http://www.enterprisedb.com/>m<http://www.enterprisedb.com/;
*
Follow us on Twitter*
@EnterpriseDB

Visit EnterpriseDB for tutorials, webinars,
whitepapers<http://www.enterprisedb.com/resources-community; and
more <http://www.enterprisedb.com/resources-community;


On Thu, May 30, 2013 at 5:39 PM, itishree sukla <itishree.sukla@gmail.com>wrote:

> Hi all,
>
> In our server Check pointer process is consuming 8 GB of memory, what
> could be the possible reason? Can any one please help.
>
> Regards,
> Itishree
>

^ permalink  raw  reply  [nested|flat] 9+ messages in thread

* Re: Check Pointer
  2013-05-30 12:09 Check Pointer itishree sukla <itishree.sukla@gmail.com>
@ 2013-05-30 12:26 ` Heikki Linnakangas <hlinnakangas@vmware.com>
  2013-05-30 12:45   ` Re: Check Pointer itishree sukla <itishree.sukla@gmail.com>
  2 siblings, 1 reply; 9+ messages in thread

From: Heikki Linnakangas @ 2013-05-30 12:26 UTC (permalink / raw)
  To: itishree sukla <itishree.sukla@gmail.com>; +Cc: pgsql-performance

On 30.05.2013 15:09, itishree sukla wrote:
> In our server Check pointer process is consuming 8 GB of memory, what could
> be the possible reason? Can any one please help.

Are you sure you're measuring the memory correctly? The RES field in top 
output, for example, includes shared memory, ie. the whole buffer cache. 
Shared memory isn't really "consumed" by the checkpointer process, but 
shared by all postgres processes.

- Heikki


-- 
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance



^ permalink  raw  reply  [nested|flat] 9+ messages in thread

* Re: Check Pointer
  2013-05-30 12:09 Check Pointer itishree sukla <itishree.sukla@gmail.com>
  2013-05-30 12:26 ` Re: Check Pointer Heikki Linnakangas <hlinnakangas@vmware.com>
@ 2013-05-30 12:45   ` itishree sukla <itishree.sukla@gmail.com>
  2013-06-06 04:44     ` Re: Check Pointer itishree sukla <itishree.sukla@gmail.com>
  2013-06-07 08:19     ` Re: Check Pointer Bernd Helmle <mailings@oopsware.de>
  0 siblings, 2 replies; 9+ messages in thread

From: itishree sukla @ 2013-05-30 12:45 UTC (permalink / raw)
  To: Heikki Linnakangas <hlinnakangas@vmware.com>; +Cc: pgsql-performance

Thanks for the quick response. Below is the out put of Top Commnd.

3971 postgres  20   0 8048m 303m 301m S    0  0.9   0:04.34
/usr/lib/postgresql/9.2/bin/postgres -D /var/lib/postgresql/9.2/main -c
config_file=/etc/postgre
 3972 postgres  20   0 66828 1820  708 S    0  0.0   1:36.37 postgres:
logger
process

 3974 postgres  20   0 8054m 7.6g 7.6g S    0 24.1   0:56.59 postgres:
checkpointer
process
 3975 postgres  20   0 8051m 895m 891m S    0  2.8   0:04.98 postgres:
writer
process

 3976 postgres  20   0 8051m   9m 9072 S    0  0.0   0:35.17 postgres: wal
writer
process
 3977 postgres  20   0 70932 3352  716 S    0  0.0   0:05.19 postgres:
stats collector
process
1

Postgresql =9.2.3



On Thu, May 30, 2013 at 5:56 PM, Heikki Linnakangas <hlinnakangas@vmware.com
> wrote:

> On 30.05.2013 15:09, itishree sukla wrote:
>
>> In our server Check pointer process is consuming 8 GB of memory, what
>> could
>> be the possible reason? Can any one please help.
>>
>
> Are you sure you're measuring the memory correctly? The RES field in top
> output, for example, includes shared memory, ie. the whole buffer cache.
> Shared memory isn't really "consumed" by the checkpointer process, but
> shared by all postgres processes.
>
> - Heikki
>

^ permalink  raw  reply  [nested|flat] 9+ messages in thread

* Re: Check Pointer
  2013-05-30 12:09 Check Pointer itishree sukla <itishree.sukla@gmail.com>
  2013-05-30 12:26 ` Re: Check Pointer Heikki Linnakangas <hlinnakangas@vmware.com>
  2013-05-30 12:45   ` Re: Check Pointer itishree sukla <itishree.sukla@gmail.com>
@ 2013-06-06 04:44     ` itishree sukla <itishree.sukla@gmail.com>
  2013-06-06 12:53       ` Re: Check Pointer Kevin Grittner <kgrittn@ymail.com>
  2013-06-07 13:53       ` Re: Check Pointer Matheus de Oliveira <matioli.matheus@gmail.com>
  1 sibling, 2 replies; 9+ messages in thread

From: itishree sukla @ 2013-06-06 04:44 UTC (permalink / raw)
  To: Heikki Linnakangas <hlinnakangas@vmware.com>; +Cc: pgsql-performance

Can any one give more input, you can see my top out put, in %MEM its taking
24.1.

Regards,
Itishree


On Thu, May 30, 2013 at 6:15 PM, itishree sukla <itishree.sukla@gmail.com>wrote:

> Thanks for the quick response. Below is the out put of Top Commnd.
>
> 3971 postgres  20   0 8048m 303m 301m S    0  0.9   0:04.34
> /usr/lib/postgresql/9.2/bin/postgres -D /var/lib/postgresql/9.2/main -c
> config_file=/etc/postgre
>  3972 postgres  20   0 66828 1820  708 S    0  0.0   1:36.37 postgres:
> logger
> process
>
>  3974 postgres  20   0 8054m 7.6g 7.6g S    0 24.1   0:56.59 postgres:
> checkpointer
> process
>  3975 postgres  20   0 8051m 895m 891m S    0  2.8   0:04.98 postgres:
> writer
> process
>
>  3976 postgres  20   0 8051m   9m 9072 S    0  0.0   0:35.17 postgres: wal
> writer
> process
>  3977 postgres  20   0 70932 3352  716 S    0  0.0   0:05.19 postgres:
> stats collector
> process
> 1
>
> Postgresql =9.2.3
>
>
>
> On Thu, May 30, 2013 at 5:56 PM, Heikki Linnakangas <
> hlinnakangas@vmware.com> wrote:
>
>> On 30.05.2013 15:09, itishree sukla wrote:
>>
>>> In our server Check pointer process is consuming 8 GB of memory, what
>>> could
>>> be the possible reason? Can any one please help.
>>>
>>
>> Are you sure you're measuring the memory correctly? The RES field in top
>> output, for example, includes shared memory, ie. the whole buffer cache.
>> Shared memory isn't really "consumed" by the checkpointer process, but
>> shared by all postgres processes.
>>
>> - Heikki
>>
>
>

^ permalink  raw  reply  [nested|flat] 9+ messages in thread

* Re: Check Pointer
  2013-05-30 12:09 Check Pointer itishree sukla <itishree.sukla@gmail.com>
  2013-05-30 12:26 ` Re: Check Pointer Heikki Linnakangas <hlinnakangas@vmware.com>
  2013-05-30 12:45   ` Re: Check Pointer itishree sukla <itishree.sukla@gmail.com>
  2013-06-06 04:44     ` Re: Check Pointer itishree sukla <itishree.sukla@gmail.com>
@ 2013-06-06 12:53       ` Kevin Grittner <kgrittn@ymail.com>
  1 sibling, 0 replies; 9+ messages in thread

From: Kevin Grittner @ 2013-06-06 12:53 UTC (permalink / raw)
  To: itishree sukla <itishree.sukla@gmail.com>; Heikki Linnakangas <hlinnakangas@vmware.com>; +Cc: pgsql-performance

itishree sukla <itishree.sukla@gmail.com> wrote:
> itishree sukla <itishree.sukla@gmail.com> wrote:
>> Heikki Linnakangas <hlinnakangas@vmware.com> wrote:
>>> itishree sukla wrote:
>>>
>>>> In our server Check pointer process is consuming 8 GB of
>>>> memory, what could be the possible reason? Can any one please
>>>> help.
>>>
>>> Are you sure you're measuring the memory correctly? The RES
>>> field in top output, for example, includes shared memory, ie.
>>> the whole buffer cache. Shared memory isn't really "consumed"
>>> by the checkpointer process, but shared by all postgres processes.
>>
>> Thanks for the quick response. Below is the out put of Top
>> Commnd.
>>
>> 3971 postgres  20   0 8048m 303m 301m S    0  0.9   0:04.34 3971 postgres  20   0 8048m 303m 301m S    0  0.9   0:04.34 /usr/lib/postgresql/9.2/bin/postgres -D /var/lib/postgresql/9.2/main -c config_file=/etc/postgre
>> 3972 postgres  20   0 66828 1820  708 S    0  0.0   1:36.37 postgres: logger process
>> 3974 postgres  20   0 8054m 7.6g 7.6g S    0 24.1   0:56.59 postgres: checkpointer process
>> 3975 postgres  20   0 8051m 895m 891m S    0  2.8   0:04.98 postgres: writer process
>> 3976 postgres  20   0 8051m   9m 9072 S    0  0.0   0:35.17 postgres: wal writer process
>> 3977 postgres  20   0 70932 3352  716 S    0  0.0   0:05.19 postgres: stats collector process

> Can any one give more input, you can see my top out put, in %MEM
> its taking 24.1.

It's not.  It's referencing all of your shared_buffers.

--
Kevin Grittner
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


-- 
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance



^ permalink  raw  reply  [nested|flat] 9+ messages in thread

* Re: Check Pointer
  2013-05-30 12:09 Check Pointer itishree sukla <itishree.sukla@gmail.com>
  2013-05-30 12:26 ` Re: Check Pointer Heikki Linnakangas <hlinnakangas@vmware.com>
  2013-05-30 12:45   ` Re: Check Pointer itishree sukla <itishree.sukla@gmail.com>
  2013-06-06 04:44     ` Re: Check Pointer itishree sukla <itishree.sukla@gmail.com>
@ 2013-06-07 13:53       ` Matheus de Oliveira <matioli.matheus@gmail.com>
  1 sibling, 0 replies; 9+ messages in thread

From: Matheus de Oliveira @ 2013-06-07 13:53 UTC (permalink / raw)
  To: itishree sukla <itishree.sukla@gmail.com>; +Cc: Heikki Linnakangas <hlinnakangas@vmware.com>; pgsql-performance

On Thu, Jun 6, 2013 at 1:44 AM, itishree sukla <itishree.sukla@gmail.com>wrote:

> Can any one give more input, you can see my top out put, in %MEM its
> taking 24.1.
>
>
> On Thu, May 30, 2013 at 6:15 PM, itishree sukla <itishree.sukla@gmail.com>wrote:
>
>> Thanks for the quick response. Below is the out put of Top Commnd.
>>
>> 3971 postgres  20   0 8048m 303m 301m S    0  0.9   0:04.34
>> /usr/lib/postgresql/9.2/bin/postgres -D /var/lib/postgresql/9.2/main -c
>> config_file=/etc/postgre
>>  3972 postgres  20   0 66828 1820  708 S    0  0.0   1:36.37 postgres:
>> logger
>> process
>>
>>  3974 postgres  20   0 8054m 7.6g 7.6g S    0 24.1   0:56.59 postgres:
>> checkpointer
>> process
>>  3975 postgres  20   0 8051m 895m 891m S    0  2.8   0:04.98 postgres:
>> writer
>> process
>>
>>  3976 postgres  20   0 8051m   9m 9072 S    0  0.0   0:35.17 postgres:
>> wal writer
>> process
>>  3977 postgres  20   0 70932 3352  716 S    0  0.0   0:05.19 postgres:
>> stats collector
>> process
>> 1
>>
>> Postgresql =9.2.3
>>
>>
>>
>> On Thu, May 30, 2013 at 5:56 PM, Heikki Linnakangas <
>> hlinnakangas@vmware.com> wrote:
>>
>>> On 30.05.2013 15:09, itishree sukla wrote:
>>>
>>>> In our server Check pointer process is consuming 8 GB of memory, what
>>>> could
>>>> be the possible reason? Can any one please help.
>>>>
>>>
>>> Are you sure you're measuring the memory correctly? The RES field in top
>>> output, for example, includes shared memory, ie. the whole buffer cache.
>>> Shared memory isn't really "consumed" by the checkpointer process, but
>>> shared by all postgres processes.
>>>
>>> - Heikki
>>>
>>
>>
>
As said before, the memory you may be not the real memory consumed by
checkpointer process, but it includes the shared memory (which is,
basically, used by all postgres' processes).
Depesz wrote a nice topic on his blog about this subject [1], read it and
try the commands to see the real memory usage by checkpointer (when I say
"real", I mean "private").

[1] http://www.depesz.com/2012/06/09/how-much-ram-is-postgresql-using/

Regards,
-- 
Matheus de Oliveira
Analista de Banco de Dados
Dextra Sistemas - MPS.Br nível F!
www.dextra.com.br/postgres

^ permalink  raw  reply  [nested|flat] 9+ messages in thread

* Re: Check Pointer
  2013-05-30 12:09 Check Pointer itishree sukla <itishree.sukla@gmail.com>
  2013-05-30 12:26 ` Re: Check Pointer Heikki Linnakangas <hlinnakangas@vmware.com>
  2013-05-30 12:45   ` Re: Check Pointer itishree sukla <itishree.sukla@gmail.com>
@ 2013-06-07 08:19     ` Bernd Helmle <mailings@oopsware.de>
  1 sibling, 0 replies; 9+ messages in thread

From: Bernd Helmle @ 2013-06-07 08:19 UTC (permalink / raw)
  To: itishree sukla <itishree.sukla@gmail.com>; Heikki Linnakangas <hlinnakangas@vmware.com>; +Cc: pgsql-performance



--On 30. Mai 2013 18:15:04 +0530 itishree sukla <itishree.sukla@gmail.com> 
wrote:

> Thanks for the quick response. Below is the out put of Top Commnd.
>
> 3971 postgres  20   0 8048m 303m 301m S    0  0.9   0:04.34
> /usr/lib/postgresql/9.2/bin/postgres -D /var/lib/postgresql/9.2/main -c
> config_file=/etc/postgre
>  3972 postgres  20   0 66828 1820  708 S    0  0.0   1:36.37
> postgres: logger
> process                                 
> 
                                    > 
 
>  3974 postgres  20   0 8054m 7.6g 7.6g S    0 24.1   0:56.59
> postgres: checkpointer
> process                                 
>                                 

On Linux i often find the pmap utility a far better tool to get an idea 
what a process
actually consumes of memory. The output can be large sometimes, but it's 
more "fine grained".


-- 
Thanks

	Bernd


-- 
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance



^ permalink  raw  reply  [nested|flat] 9+ messages in thread


end of thread, other threads:[~2013-06-07 13:53 UTC | newest]

Thread overview: 9+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2013-05-30 12:09 Check Pointer itishree sukla <itishree.sukla@gmail.com>
2013-05-30 12:20 ` Greg Smith <greg@2ndQuadrant.com>
2013-05-30 12:20 ` Dinesh Kumar <dinesh.kumar@enterprisedb.com>
2013-05-30 12:26 ` Heikki Linnakangas <hlinnakangas@vmware.com>
2013-05-30 12:45   ` itishree sukla <itishree.sukla@gmail.com>
2013-06-06 04:44     ` itishree sukla <itishree.sukla@gmail.com>
2013-06-06 12:53       ` Kevin Grittner <kgrittn@ymail.com>
2013-06-07 13:53       ` Matheus de Oliveira <matioli.matheus@gmail.com>
2013-06-07 08:19     ` Bernd Helmle <mailings@oopsware.de>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox