X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id F24AB52A59 for ; Fri, 25 Feb 2005 07:41:50 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 64141-08 for ; Fri, 25 Feb 2005 07:41:45 +0000 (GMT) Received: from hotmail.com (bay14-dav7.bay14.hotmail.com [64.4.48.111]) by svr1.postgresql.org (Postfix) with ESMTP id EA56852A54 for ; Fri, 25 Feb 2005 07:41:44 +0000 (GMT) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Thu, 24 Feb 2005 23:42:01 -0800 Message-ID: Received: from 144.136.239.156 by BAY14-DAV7.phx.gbl with DAV; Fri, 25 Feb 2005 07:41:56 +0000 X-Originating-IP: [144.136.239.156] X-Originating-Email: [space_ball_one@hotmail.com] X-Sender: space_ball_one@hotmail.com From: "SpaceBallOne" To: Subject: gah! sudden slowdown?? Date: Fri, 25 Feb 2005 15:41:58 +0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0025_01C51B50.8A4839D0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-OriginalArrivalTime: 25 Feb 2005 07:42:01.0021 (UTC) FILETIME=[7DDEDED0:01C51B0D] X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=4.555 tagged_above=0 required=5 tests=AWL, DNS_FROM_RFC_POST, FORGED_MUA_OUTLOOK, HTML_50_60, HTML_MESSAGE, MSGID_FROM_MTA_HEADER, PLING_QUERY X-Spam-Level: **** X-Archive-Number: 200502/356 X-Sequence-Number: 10685 This is a multi-part message in MIME format. ------=_NextPart_000_0025_01C51B50.8A4839D0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Our dual opteron has been performing well for many weeks now (after some = simple tuning) when all of a sudden the queries have slowed right down! ie: DUAL 246 OPTERON: select count(*) from job_archieve; - Time: 107.24 ms explain analyse select count(*) from job_archieve; Aggregate (cost=3D2820.50..2820.50 rows=3D1 width=3D0) (actual = time=3D153.53..153.53 rows=3D1 loops=3D1) -> Seq Scan on job_archieve (cost=3D0.00..2789.20 rows=3D12520 = width=3D0) (actual time=3D1.39..132.98 rows=3D12520 loops=3D1) Total runtime: 153.74 msec Time: 156.94 ms CRAPPY AMD ATHLON XP 1700+: select count(*) from job_archieve; - Time: 23.30 ms explain analyse select count(*) from job_archieve; Aggregate (cost=3D2816.50..2816.50 rows=3D1 width=3D0) (actual = time=3D133.83..133.84 rows=3D1 loops=3D1) -> Seq Scan on job_archieve (cost=3D0.00..2785.20 rows=3D12520 = width=3D0) (actual time=3D0.02..72.64 rows=3D12520 loops=3D1) Total runtime: 133.92 msec Time: 134.79 ms The ratio of these simple query times is about accurate for most queries = performed on the same database on the different machines... Any ideas = what may have suddenly caused this and where to start troubleshooting??? = Both dbs have already been fully vacuumed. The opteron is going to get a overhaul (4 port raid going in, fresh = install of freebsd, postgres etc) but would be handy to know for future = reference in case this happens again.... (ps, yes i know archive is not spelt archieve ;) Cheers! Dave. ------=_NextPart_000_0025_01C51B50.8A4839D0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Our dual opteron has been performing = well for many=20 weeks now (after some simple tuning) when all of a sudden the queries = have=20 slowed right down!

ie:
 
DUAL 246 OPTERON:
 
select count(*) from job_archieve; - = Time: 107.24 ms
 
explain analyse select count(*) from=20 job_archieve;
Aggregate  (cost=3D2820.50..2820.50 rows=3D1 = width=3D0) (actual=20 time=3D153.53..153.53 rows=3D1 loops=3D1)
   ->  = Seq Scan on=20 job_archieve  (cost=3D0.00..2789.20 rows=3D12520 width=3D0) (actual = time=3D1.39..132.98 rows=3D12520 loops=3D1)
 Total runtime: = 153.74=20 msec
Time: 156.94 ms
 
 
 
CRAPPY AMD ATHLON XP = 1700+:
 
select count(*) from job_archieve; - = Time: 23.30 ms
 
explain analyse select count(*) from=20 job_archieve;
Aggregate  = (cost=3D2816.50..2816.50 rows=3D1=20 width=3D0) (actual time=3D133.83..133.84 rows=3D1 = loops=3D1)
   -> =20 Seq Scan on job_archieve  (cost=3D0.00..2785.20 rows=3D12520 = width=3D0) (actual=20 time=3D0.02..72.64 rows=3D12520 loops=3D1)
 Total runtime: = 133.92=20 msec
Time: 134.79 ms
 
 
 
 
 
The ratio of these simple query times = is about=20 accurate for most queries performed on the same database on the = different=20 machines... Any ideas what may have suddenly caused this and where to = start=20 troubleshooting??? Both dbs have already been fully = vacuumed.
 
The opteron is going to get a overhaul = (4 port raid=20 going in, fresh install of freebsd, postgres etc) but would be handy to = know for=20 future reference in case this happens again....
 
(ps, yes i know archive is not spelt = archieve=20 ;)
 
Cheers!
Dave.
 



------=_NextPart_000_0025_01C51B50.8A4839D0--