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

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

From: "Joel Fradkin" <jfradkin(at)wazagua(dot)com>
To: "'Mohan, Ross'" <RMohan(at)arbinet(dot)com>, <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: [PERFORM] Joel's Performance Issues WAS : Opteron vs Xeon
Date: 2005-04-23 14:18:31
Message-ID: 001801c5480f$54573d80$797ba8c0@jfradkin (view raw or flat)
Thread:
Lists: pgsql-odbcpgsql-performance
Hate to be dumb, but unfortunately I am.

Could you give me an idea what I should be using, or is there a good
resource for me to check out.
I have been spending so much time with config and moving data, converting
etc, I never looked at the odbc settings (didn't even think about it until
Josh brought it up). I did ask him for his advice, but would love a second
opinion.

Our data is a bit of a mixture, some records have text items most are
varchars and integers with a bit of Booleans mixed in.

I am running 8.0.2 so not sure if the protocol is ODBC or Postgres?

Thanks for responding I appreciate any help 

Joel Fradkin
 
-----Original Message-----
From: pgsql-odbc-owner(at)postgresql(dot)org
[mailto:pgsql-odbc-owner(at)postgresql(dot)org] On Behalf Of Mohan, Ross
Sent: Thursday, April 21, 2005 10:01 AM
To: pgsql-odbc(at)postgresql(dot)org
Subject: Re: [ODBC] [PERFORM] Joel's Performance Issues WAS : Opteron vs
Xeon

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;BoolsAs
Char=1;Parse=0;CancelAsFreeStmt=;ExtraSysTablePrefixes=dd_;LFConversion=1;Up
datableCursors=1;DisallowPremature=0;TrueIsMinus1=0;BI=0;ByteaAsLongVarBinar
y=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....






---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings


In response to

Responses

pgsql-performance by date

Next:From: Joshua D. DrakeDate: 2005-04-23 15:35:52
Subject: Re: Joel's Performance Issues WAS : Opteron vs Xeon
Previous:From: Joel FradkinDate: 2005-04-23 14:11:28
Subject: Re: Joel's Performance Issues WAS : Opteron vs Xeon

pgsql-odbc by date

Next:From: Typing80wpmDate: 2005-04-23 14:37:56
Subject: Ambiguities in ODBC Install Parameters
Previous:From: Marko RistolaDate: 2005-04-23 06:57:11
Subject: Re: Bound column and serial datatype question

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