Skip site navigation (1) Skip section navigation (2)

Re: [PERFORM] Joel's Performance Issues WAS : Opteron vs Xeon

From: "Mohan, Ross" <RMohan(at)arbinet(dot)com>
To: <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: [PERFORM] Joel's Performance Issues WAS : Opteron vs Xeon
Date: 2005-04-21 15:01:10
Message-ID: CC74E7E10A8A054798B6611BD1FEF4D30625DA6C@vamail01.thexchange.com (view raw or flat)
Thread:
Lists: pgsql-odbcpgsql-performance
Joel, thanks. A couple of things jump out there for
me, not a problem for a routine ODBC connection, but
perhaps in the "lotsa stuff" context of your current
explorations, it might be relevant?

I am completely shooting from the hip, here, but...if
it were my goose to cook, I'd be investigating

Session("StringConn") = "DRIVER={PostgreSQL};DATABASE=wazagua;SERVER=192.168.123.252;PORT=5432;UID=;
PWD=;ReadOnly=0;Protocol=6.4;

|| Protocol? Is this related to version? is the driver waaaay old?


FakeOidIndex=0;ShowOidColumn=0;RowVersioning=0;
ShowSystemTables=0;ConnSettings=;Fetch=100;

||  Fetch great for OLTP, lousy for batch?


Socket=4096;UnknownSizes=0;MaxVarcharSize=254;MaxLongVarcharSize=8190;

||  what ARE the datatypes and sizes in your particular case? 

Debug=0;

||  a run with debug=1 probably would spit up something interesting....

CommLog=0;Optimizer=1;

||  Optimizer? that's a new one on me....

Ksqo=1;UseDeclareFetch=0;TextAsLongVarchar=1;UnknownsAsLongVarchar=0;BoolsAsChar=1;Parse=0;CancelAsFreeStmt=;ExtraSysTablePrefixes=dd_;LFConversion=1;UpdatableCursors=1;DisallowPremature=0;TrueIsMinus1=0;BI=0;ByteaAsLongVarBinary=0;UseServerSidePrepare=0"

||  that's about all I can see, prima facie.  I'll be very curious to know if ODBC is
   any part of your performance equation. 


HTH, 

Ross

-----Original Message-----
From: Joel Fradkin [mailto:jfradkin(at)wazagua(dot)com] 
Sent: Thursday, April 21, 2005 10:54 AM
To: Mohan, Ross
Cc: pgsql-odbc(at)postgresql(dot)org; PostgreSQL Perform
Subject: RE: [PERFORM] Joel's Performance Issues WAS : Opteron vs Xeon


Here is the connect string I am using.
It could be horrid as I cut it from ODBC program.

Session("StringConn") = "DRIVER={PostgreSQL};DATABASE=wazagua;SERVER=192.168.123.252;PORT=5432;UID=;
PWD=;ReadOnly=0;Protocol=6.4;FakeOidIndex=0;ShowOidColumn=0;RowVersioning=0;
ShowSystemTables=0;ConnSettings=;Fetch=100;Socket=4096;UnknownSizes=0;MaxVar
charSize=254;MaxLongVarcharSize=8190;Debug=0;CommLog=0;Optimizer=1;Ksqo=1;Us
eDeclareFetch=0;TextAsLongVarchar=1;UnknownsAsLongVarchar=0;BoolsAsChar=1;Pa
rse=0;CancelAsFreeStmt=0;ExtraSysTablePrefixes=dd_;LFConversion=1;UpdatableC
ursors=1;DisallowPremature=0;TrueIsMinus1=0;BI=0;ByteaAsLongVarBinary=0;UseS
erverSidePrepare=0"

Joel Fradkin
 

-----Original Message-----
From: Mohan, Ross [mailto:RMohan(at)arbinet(dot)com] 
Sent: Thursday, April 21, 2005 9:42 AM
To: jfradkin(at)wazagua(dot)com
Subject: RE: [PERFORM] Joel's Performance Issues WAS : Opteron vs Xeon

FWIW, ODBC has variables to tweak, as well. fetch/buffer sizes, and the like. 

Maybe one of the ODBC cognoscenti here can chime in more concretely....






Responses

pgsql-performance by date

Next:From: Shoaib Burq (VPAC)Date: 2005-04-21 15:01:19
Subject: Re: two queries and dual cpu (perplexed)
Previous:From: Joel FradkinDate: 2005-04-21 14:53:51
Subject: Re: [PERFORM] Joel's Performance Issues WAS : Opteron vs Xeon

pgsql-odbc by date

Next:From: Petr OdloĹžilDate: 2005-04-22 12:46:34
Subject: ForwardOnly ?
Previous:From: Joel FradkinDate: 2005-04-21 14:53:51
Subject: Re: [PERFORM] Joel's Performance Issues WAS : Opteron vs Xeon

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group