Re: PostgreSQL backend process high memory usage issue

From: Shianmiin <Shianmiin(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: PostgreSQL backend process high memory usage issue
Date: 2011-04-08 15:30:00
Message-ID: 1302276600400-4291173.post@n5.nabble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-general


Shianmiin wrote:
>
> Hi Merlin,
>
> I revised the test code with attached files and use pgbench to send the
> test queries.
>
> http://postgresql.1045698.n5.nabble.com/file/n4290723/dotest dotest
> http://postgresql.1045698.n5.nabble.com/file/n4290723/initialize.sql
> initialize.sql
> http://postgresql.1045698.n5.nabble.com/file/n4290723/test.sql test.sql
>
> Samuel
>

Just want to put some descriptions on the revised test code:

1. This test is not a real life testing, it's is specifically designed to
emphasize the high memory usage issue of PostgreSQL backend process we
encountered.
2. The tests in the dotest file uses pgbench's feature to simulate 20
concurrent clients sending random queries, which will make the host memory
usage climb even faster; eventually all 20 concurrent PostgreSQL process
will all use 1.5 GB (30GB in total). To do the same tests as in the original
post, we can run

pgbench memoryusagetest -c 1 -j 1 -T180 -f test.sql

Samuel

--
View this message in context: http://postgresql.1045698.n5.nabble.com/PostgreSQL-backend-process-high-memory-usage-issue-tp4289407p4291173.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Merlin Moncure 2011-04-08 18:39:52 Re: PostgreSQL backend process high memory usage issue
Previous Message genamiga 2011-04-08 15:21:34 Re: BUG #5800: "corrupted" error messages (encoding problem ?)

Browse pgsql-general by date

  From Date Subject
Next Message Jason Long 2011-04-08 16:39:26 comma vs cross join question
Previous Message Shianmiin 2011-04-08 15:03:36 Re: PostgreSQL backend process high memory usage issue