Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 8121963261D for ; Sun, 1 Mar 2009 13:57:12 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 19238-05 for ; Sun, 1 Mar 2009 13:57:08 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from linos.es (centrodatos.linos.es [86.109.105.97]) by mail.postgresql.org (Postfix) with ESMTP id F27B06325CE for ; Sun, 1 Mar 2009 13:57:07 -0400 (AST) Received: (qmail 25592 invoked from network); 1 Mar 2009 18:37:08 +0100 Received: from 230.87.220.87.dynamic.jazztel.es (HELO ?192.168.1.4?) (info@linos.es@87.220.87.230) by linos.es with SMTP; 1 Mar 2009 18:37:08 +0100 Message-ID: <49AACC6F.7080809@linos.es> Date: Sun, 01 Mar 2009 18:57:03 +0100 From: Linos User-Agent: Thunderbird 2.0.0.19 (X11/20090213) MIME-Version: 1.0 To: Tom Lane CC: "Ross J. Reedstrom" , pgsql-performance@postgresql.org Subject: Re: TCP network cost References: <1ca1c1410902171013q478f2620n13fcd68cb8b3d911@mail.gmail.com> <20090217070403.GB2486@cooker> <3FAF940B-9B0B-4DBA-8728-6096022129DF@infogears.com> <20090217070403.GB2486@cooker> <3FAF940B-9B0B-4DBA-8728-6096022129DF@infogears.com> <20090217200416.GA23707@cooker> <87hc2r272g.fsf@oxford.xeocode.com> <20090223194212.GA14802@cooker> <27042.1235423820@sss.pgh.pa.us> <20090224170201.GA25420@cooker> <49AAC6AC.60309@linos.es> <13121.1235929398@sss.pgh.pa.us> In-Reply-To: <13121.1235929398@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200903/4 X-Sequence-Number: 32926 Tom Lane escribió: > Linos writes: >> Hello, i have been having a problem like this in debian machines and i have >> discovered that (almost in my case), the problem only arises when i am using >> "ssl = true" in postgresql.conf although i am using clear tcp connections to >> localhost to perform my query, if i disable ssl in configuration my localhost >> query times goes from 4200ms to 110ms, > > Does that number include connection startup overhead? (If it doesn't, > it'd be pretty strange.) Ross's problem is not about startup overhead, > unless I've misread him completely. > > regards, tom lane This difference it is from the runtime of the query, i get this with \timing parameter in psql, it is from a table that have 300 small png (one for every row in table) on a bytea column but the problem grows with any large result anyway, i have attacted pcap files in general list but the differences are like this: ssl enabled: `psql -d database`: SELECT * FROM TABLE (110 ms with \timing) `psql -d database -h localhost`: SELECT * FROM TABLE (4200 ms with \timing) ssl disabled: `psql -d database`: SELECT * FROM TABLE (110 ms with \timing) `psql -d database -h localhost`: SELECT * FROM TABLE (120 ~ 130 ms with \timing) Anyway i dont know if this apply to Ross problem but reading his post and after see that he is using debian and have problem with speed on tcp localhost i suppose that maybe have the same problem. Regards, Miguel Angel