Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: bad performance with sqlplus on solaris

Re: bad performance with sqlplus on solaris

From: Svend Jensen <svend.s.jensen_at_it.dk>
Date: Sun, 11 Jan 2004 13:09:24 +0100
Message-ID: <40013ca4$0$174$edfadb0f@dread11.news.tele.dk>


Chris wrote:
> "computer person" <fake_address_at_nothing.com> wrote in message
> news:eJ5Jb.256601$ea%.219724_at_news01.bloor.is.net.cable.rogers.com...
>

>>Hi,
>>
>>We are migrating our systems from aix4.3.3 to solaris8. During migration

>
> we
>
>>noticed that the sqlplus queries take a lot longer with the Solaris client
>>then with the aix sqlplus. This was proved by running the same query

>
> against
>
>>the solaris db server from a solaris client and aix and tabulating the
>>results.
>>
>>We found 1 thing that slowed it down and adjusted the SQL accordingly. The
>>LINESIZE was set real high even though the result set was only 250 bytes

>
> max
>
>>(columns). This yielded very good results but we are looking for some more
>>improvment, if possible.
>>
>>Any stories of people that use SQLPLUS on solaris and have gone through

>
> some
>
>>tuning with the client and got good results? Looks like our db server is
>>working well with exception of this.
>>
>>Thanks
>>
>>

>
> All thing being equal ie same network speed etc, then you may have a
> parameter like arraysize set wrong.
> Run autotrace on and have a look at your statistics when you try different
> arraysize.
> Asktom has a thread about this issue
> http://asktom.oracle.com/pls/ask/f?p=4950:8:5020821875913409326::NO::F4950_P
> 8_DISPLAYID,F4950_P8_CRITERIA:880343948514,
>
>

Could be a mismatch in tcp/ip package size. Oracle has default setting ip mtu (max transfer unit) of 2k bytes. Thin/twisted 10/100 network has mtu of 1500 bytes. Metalink recommends setting the mtu at 1461 for dedicated servers and 1460 for shared/multithreaded server. You can configure the listener and client to utilize a mtu of ~146x bytes, or whatever is fitting for your network. Se the docs on network, search for MTU.
Check the tnsnames.ora - avoid aliases as dbserver7, use static ip if possible. That saves a roundtrip to the name server. Check the default gateway - maybe your resultset is on a longer roundtrip/detour in the network. Traceroute is a nice tool. And netstat. Try from both ends, including both client types.

Rgds
/Svend
svend.jensen_at_SPAMKILLsecret.dk Received on Sun Jan 11 2004 - 06:09:24 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US