postgres-xc-developers Mailing List for Postgres-XC

On 1/7/11 1:45 PM, Koichi Suzuki wrote:
> Hi, (I hope this finally succeeds)
>
> Sudo-san ran DBT-1 with the latest HEAD with stability3.patch
> from Andrei (sorry it may be local so some of the readers may not know).
>  We observed no error but also found specific data node processes are
> consuming most of CPUs, as found in ps and top list attached.  Andrei,
> do you have any suggestion how it was introduced?
>
Abbas and I tried to reproduce this on my laptop by setting low timeout
values, but were not successfully. The easiest thing to do is to attach
to the processes with gdb and see what they are doing.

Regards,

Mason



> Other test environment data is as follows:
>
> PGXC
>   commit 45e1d4e389e966d072aaf98a49d9702aa253d976
>   Author: Mason Sharp <ma...@us...>
>   Date:   Thu Dec 23 15:10:38 2010 -0500
>
> Additional Patch
>   stability3.patch (from Andrei)
>
> Hardwares and configuration
>   PGXC : Co5/Dn5 (coordinator1,2,3,4,5)
>   Loader : loader1, 2
>   GtmProxy使用
>
> DBT1 parameters
>   rampup time 5分、測定時間 5分、合計10分の測定
>
>   transaction_queue_size : 2000
>   transaction_array_size : 2000
>   [dbdriver]
>   items : 10000
>   customers : 28800
>   eu : 500
>   eu/min : 100
>   mean think_tim : 0.5
>   run_duration in seconds : 300
>   access mode : access_appServer
>   access_clean
>
> -------------
> Following are picked-up lines of ps output.  Whole output will be found
> in the attached file.
> (only for coordinator1 and coordinator2)
>
> To indicate the data, ran
> date; ps ux to get the list.
>
> Kind Regards;
> ---
> Koichi Suzuki
>
> # I tried to send this file in several previous mails with tarball, but
> somehow the file was trimmed considerably and many mail-system found it
> could be bad one.   I changed the format to zip and I hope this works.
>
> I apologize if anyone received corrupted file many times.
>
> =========================================================
> Hostname: coordinator1
>   Fri Jan  7 16:08:15 JST 2011
>   USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
>   502       4957 84.4  0.0 226404  9144 ?        Rs   16:08   0:08
> postgres: sudoutaka dbt1 192.168.247.72(60593) SELECT
>   502       4965 79.6  0.0 226344  8968 ?        Rs   16:08   0:04
> postgres: sudoutaka dbt1 192.168.247.71(57079) SELECT
>   502       4971 62.0  0.0 226432  8876 ?        Rs   16:08   0:02
> postgres: sudoutaka dbt1 192.168.247.73(34752) SELECT
>
>   Fri Jan  7 16:08:45 JST 2011
>   USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
>   502       4957 29.5  0.0 226204  9280 ?        Ss   16:08   0:11
> postgres: sudoutaka dbt1 192.168.247.72(60593) idle
>   502       4965 32.8  0.0 226144  9216 ?        Ss   16:08   0:11
> postgres: sudoutaka dbt1 192.168.247.71(57079) idle
>   502       4971 34.6  0.0 226212  9276 ?        Ss   16:08   0:11
> postgres: sudoutaka dbt1 192.168.247.73(34752) idle in transaction
>   502       4986 41.1  0.0 226148  9236 ?        Ss   16:08   0:11
> postgres: sudoutaka dbt1 192.168.247.75(48995) idle
>   502       4990 44.0  0.0 226148  9224 ?        Ss   16:08   0:11
> postgres: sudoutaka dbt1 192.168.247.73(34781) idle in transaction
>   502       4995 49.0  0.0 226212  9284 ?        Ss   16:08   0:11
> postgres: sudoutaka dbt1 192.168.247.72(60651) idle
>   502       5018 20.0  0.0 226148 11680 ?        Ss   16:08   0:00
> postgres: sudoutaka dbt1 192.168.247.74(48020) idle in transaction
>
> Hostname: coordinator2
>   Fri Jan  7 16:07:33 JST 2011
>   USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
>   502      18933 80.1  0.0 226324  9164 ?        Rs   16:07   0:08
> postgres: sudoutaka dbt1 192.168.247.72(60619) SELECT
>   502      18940 54.0  0.0 226324  8908 ?        Rs   16:07   0:03
> postgres: sudoutaka dbt1 192.168.247.71(34207) SELECT
>   502      18944 81.6  0.0 226132 10848 ?        Rs   16:07   0:04
> postgres: sudoutaka dbt1 192.168.247.71(34214) SELECT
>   502      18946 80.0  0.0 226412  8920 ?        Rs   16:07   0:03
> postgres: sudoutaka dbt1 192.168.247.73(48371) SELECT
>
> 　Fri Jan  7 16:08:03 JST 2011
>   USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
>   502      18927 31.1  0.1 226196 15980 ?        Ss   16:07   0:13
> postgres: sudoutaka dbt1 192.168.247.73(58650) idle in transaction
>   502      18933 30.2  0.0 226124  9252 ?        Ss   16:07   0:12
> postgres: sudoutaka dbt1 192.168.247.72(60619) idle
>   502      18940 34.8  0.0 226124  9304 ?        Ss   16:07   0:12
> postgres: sudoutaka dbt1 192.168.247.71(34207) idle
>   502      18944 51.4  0.0 226076 11060 ?        Ss   16:07   0:18
> postgres: sudoutaka dbt1 192.168.247.71(34214) idle in transaction
>   502      18946 70.2  0.1 226192 15124 ?        Rs   16:07   0:23
> postgres: sudoutaka dbt1 192.168.247.73(48371) SELECT
>   502      18957 43.4  0.0 226128  9248 ?        Ss   16:07   0:12
> postgres: sudoutaka dbt1 192.168.247.75(58779) idle
>


-- 
Mason Sharp
EnterpriseDB Corporation
The Enterprise Postgres Company


This e-mail message (and any attachment) is intended for the use of
the individual or entity to whom it is addressed. This message
contains information from EnterpriseDB Corporation that may be
privileged, confidential, or exempt from disclosure under applicable
law. If you are not the intended recipient or authorized to receive
this for the intended recipient, any use, dissemination, distribution,
retention, archiving, or copying of this communication is strictly
prohibited. If you have received this e-mail in error, please notify
the sender immediately by reply e-mail and delete this message.