Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 600256323AE for ; Sun, 30 May 2010 23:44:05 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 78968-02 for ; Mon, 31 May 2010 02:43:55 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-pv0-f174.google.com (mail-pv0-f174.google.com [74.125.83.174]) by mail.postgresql.org (Postfix) with ESMTP id 71BE762D9D2 for ; Sun, 30 May 2010 23:43:57 -0300 (ADT) Received: by pvg11 with SMTP id 11so1142680pvg.19 for ; Sun, 30 May 2010 19:43:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:cc:references:subject :date:message-id:mime-version:content-type:x-mailer:thread-index :in-reply-to:x-mimeole; bh=mzytjxji7EhUz0oKx/PJ+oRC3pmHN5Y0QsHCW9dzgn8=; b=aAXqdZWtCSystswJnE7m0NuC/kRXVe3yzJxRmETvFStG9+RS3aOwIHEFvkuxiwD6Vt 7irSz4CdG+brZBuL+U8cbcDvJ8UDHT1y2esTBn+I6YBbrHZ9ZXUj96ICxcVMCRyIXsY0 Z3Gkz4Il/JwodB8I2GNUo2r6r34sf70SZP2EI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:references:subject:date:message-id:mime-version :content-type:x-mailer:thread-index:in-reply-to:x-mimeole; b=DkjfHCezWw0kpdQYXI92hmQzipYFZF7hknO59T2Es4QaIkh66PI6riymUZ7MXzgKBQ 5cfqe0u7Oc/S1iHB2sE0WJ9QefLYw6bF1m456L78gwdY7M9ekMOkVdCmDd5RwPfUcwxY DWxGCDi8l7DG2cEpD/AaOCvqg4r5kXmpZgL0Y= Received: by 10.143.25.2 with SMTP id c2mr2496683wfj.147.1275273835376; Sun, 30 May 2010 19:43:55 -0700 (PDT) Received: from NECSLGZ0061411 (mx.gtmc.com.cn [58.62.17.14]) by mx.google.com with ESMTPS id e16sm1443621wfg.2.2010.05.30.19.43.51 (version=SSLv3 cipher=RC4-MD5); Sun, 30 May 2010 19:43:53 -0700 (PDT) From: =?UTF-8?B?6buE5rC45Y2r?= To: =?UTF-8?Q?'I=C3=B1igo_Martinez_Lasala'?= Cc: "'pgsql-admin'" References: <62F94C41871A4EF1BECEF463739B7A47@NECSLGZ0061411> <1275032584.19383.71.camel@deimos> Subject: =?UTF-8?Q?=E7=AD=94=E5=A4=8D:_About_=22Context-switch_storm=22?= =?UTF-8?Q?_problem?= Date: Mon, 31 May 2010 10:43:55 +0800 Message-ID: <0B6FD27EE04F46298DD48C670E44F559@NECSLGZ0061411> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0050_01CB00AE.2C5C5830" X-Mailer: Microsoft Office Outlook 11 Thread-Index: Acr+OW0SvREFZxj2QGWnZzYoXCn+4QCLJCOQ In-Reply-To: <1275032584.19383.71.camel@deimos> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5931 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=1.782 tagged_above=-10 required=5 tests=BAYES_50=0.8, HTML_FONT_FACE_BAD=0.981, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001 X-Spam-Level: * X-Archive-Number: 201005/294 X-Sequence-Number: 34767 This is a multi-part message in MIME format. ------=_NextPart_000_0050_01CB00AE.2C5C5830 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Dear I=C3=B1igo Martinez Lasala=EF=BC=8C Thank you for your replay and advice.=20 My company is a software application vendor, and our customer is useing = PostgreSQL 8.1.3. When our application is runing , the DB sluggish suddenly and = application stop. To prove that it is not the problem of the application = ,We need some evidence to certified this version have problem and show = to our customer. And Can I ask you several questions? =20 1=E3=80=81 Can you recreate the "Context-switch storm" in the your = old version PostgreSQL 8.1.15 ? 2=E3=80=81 If you can ,could you please tell me your test case = =EF=BC=9F =20 Thank you so much=EF=BC=81 =20 Best regards, Ray Huang =20 _____ =20 =E5=8F=91=E4=BB=B6=E4=BA=BA: I=C3=B1igo Martinez Lasala = [mailto:imartinez@vectorsf.com]=20 =E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4: 2010=E5=B9=B45=E6=9C=8828=E6=97=A5 = 15:43 =E6=94=B6=E4=BB=B6=E4=BA=BA: =E9=BB=84=E6=B0=B8=E5=8D=AB =E6=8A=84=E9=80=81: pgsql-admin =E4=B8=BB=E9=A2=98: Re: About "Context-switch storm" problem =20 Hi, Yongwei We finally upgraded our database server to last PostgreSQL 8.2 = available. Since 8.2 does not include any major change (8.3 does indeed a lot of = them) we had no problem with this upgrade. And believe, our database was = really complex. About 600 tables with 300 stored procedures, wide use of = embedded functions from different packages (including tsearch2) and lot = of triggers and views. Not problems at all.=20 Migrating to 8.3 or 8.4 is another history. So, my recommendation is to = migrate to 8.2.17 -----Original Message----- From: =E9=BB=84=E6=B0=B8=E5=8D=AB > To: imartinez@vectorsf.com Subject: About "Context-switch storm" problem Date: Fri, 28 May 2010 13:31:54 +0800 Hello=EF=BC=8CI=C3=B1igo Martinez Lasala ! =20 I read your mail about =E2=80=9CContext-switch storm in 8.1.15=E2=80=9D = from postgres website. I think I meet the same problem as you now . Recently my company=E2=80=99s postgres DB server sluggish suddenly with = a hight Context-switching value as below: =20 2010-04-07 04:03:15 procs memory swap = io system cpu 2010-04-07 04:03:15 r b swpd free buff cache si so bi = bo in cs us sy id wa 2010-04-07 14:04:27 3 0 0 2361272 272684 3096148 0 0 3 = 1445 973 14230 7 8 84 0 2010-04-07 14:05:27 2 0 0 2361092 272684 3096220 0 0 3 = 1804 1029 31852 8 10 81 1 2010-04-07 14:06:27 1 0 0 2362236 272684 3096564 0 0 3 = 1865 1135 19689 9 9 81 0 2010-04-07 14:07:27 1 0 0 2348400 272720 3101836 0 0 3 = 1582 1182 149461 15 17 67 0 2010-04-07 14:08:27 3 0 0 2392028 272840 3107600 0 0 3 = 3093 1275 203196 24 23 53 1 2010-04-07 14:09:27 3 1 0 2386224 272916 3107960 0 0 3 = 2486 1331 193299 26 22 52 0 2010-04-07 14:10:27 34 0 0 2332320 272980 3107944 0 0 3 = 1692 1082 214309 24 22 54 0 2010-04-07 14:11:27 1 0 0 2407432 273028 3108092 0 0 6 = 2770 1540 76643 29 13 57 1 2010-04-07 14:12:27 9 0 0 2358968 273104 3108388 0 0 7 = 2639 1466 10603 22 6 72 1 =20 =20 I May I know your solution after that ? =20 =20 =20 Thank you ! Best wishes, Ray Huang ------=_NextPart_000_0050_01CB00AE.2C5C5830 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Dear I=C3=B1igo Martinez = Lasala=EF=BC=8C

=C2=A0=C2=A0=C2=A0 Thank you for = your replay and advice.

My company is a software application vendor, and our = customer =C2=A0is useing PostgreSQL 8.1.3.

When our application = is runing , the DB sluggish suddenly and application = stop.

To prove t= hat it is not the problem of the application ,We need some evidence to = certified this version have problem and show to our = customer.

=C2=A0=C2=A0=C2=A0 And Can = =C2=A0I ask you =C2=A0several  = questions?

 

1=E3=80=81  = Can you recreate = the =C2=A0"Context-switch storm" in the =C2=A0your old version PostgreSQL 8.1.15 ?

2=E3=80=81  = If you can ,could = you please tell me your test case =EF=BC=9F

 

Thank you so = much=EF=BC=81

 

Best = regards,

Ray = Huang

 

=

=E5=8F=91=E4=BB=B6=E4=BA=BA: I=C3=B1igo Martinez Lasala [mailto:imartinez@vectorsf.com]
=E5=8F=91=E9=80=81=E6=97=B6=E9= =97=B4: 2010=E5=B9=B45=E6=9C=8828=E6=97=A5 15:43
=E6=94=B6=E4=BB=B6=E4=BA=BA: =E9=BB=84=E6=B0=B8=E5=8D=AB
=E6=8A=84=E9=80=81: pgsql-admin
=E4=B8=BB=E9=A2=98: Re: About "Context-switch storm" = problem

 

Hi, Yongwei

We finally upgraded our database server to last PostgreSQL 8.2 = available.

Since 8.2 does not include any major change (8.3 does indeed a lot of = them) we had no problem with this upgrade. And believe, our database was really = complex. About 600 tables with 300 stored procedures, wide use of embedded = functions from different packages (including tsearch2) and lot of triggers and = views. Not problems at all.

Migrating to 8.3 or 8.4 is another history. So, my recommendation is to = migrate to 8.2.17

-----Original Message-----
From: = =E9=BB=84=E6=B0=B8=E5=8D=AB <yongwei.huang@gmail.com&= gt;
To: imartinez@vectorsf.com
Subject: About "Context-switch storm" problem
Date: Fri, 28 May 2010 = 13:31:54 +0800

Hello=EF=BC=8CI=C3=B1igo Martinez Lasala !

   

I read your mail about =E2=80=9CContext-switch storm in = 8.1.15=E2=80=9D from = postgres website.

I think I meet the same problem as you now = .

Recently my = company=E2=80=99s  postgres DB server sluggish suddenly with a hight Context-switching value as = below:

 

2010-04-07 04:03:15 procs           &n= bsp;          memory      swap          io =     system       &= nbsp; cpu

2010-04-07 04:03:15  = r  b   swpd   free   buff  = cache   si   so    bi    bo   in    cs us sy id wa

2010-04-07 14:04:27  = 3  0      0 2361272 272684 = 3096148    0    0     3  1445  973 14230  7  8 84  0

2010-04-07 14:05:27  = 2  0      0 2361092 272684 = 3096220    0    0     3  1804 1029 = 31852  8 10 81  1

2010-04-07 14:06:27  = 1  0      0 2362236 272684 = 3096564    0    0     3  1865 1135 = 19689  9  9 81  0

2010-04-07 14:07:27  = 1  0      0 2348400 272720 = 3101836    0    0     3  1582 1182 149461 = 15 17 67  0

2010-04-07 14:08:27  = 3  0      0 2392028 272840 = 3107600    0    0     3  3093 1275 203196 = 24 23 53  1

2010-04-07 14:09:27  = 3  1      0 2386224 272916 = 3107960    0    0     3  2486 1331 193299 = 26 22 52  0

2010-04-07 14:10:27 = 34  0      0 2332320 272980 = 3107944    0    0     3  1692 1082 214309 = 24 22 54  0

2010-04-07 14:11:27  = 1  0      0 2407432 273028 = 3108092    0    0     6  2770 1540 76643 29 = 13 57  1

2010-04-07 14:12:27  = 9  0      0 2358968 273104 = 3108388    0    0     7  2639 1466 10603 = 22  6 72  1

 

 

I

May I know your solution after  that = ?

 

 

 

Thank you !

Best wishes,

Ray Huang


------=_NextPart_000_0050_01CB00AE.2C5C5830--