oracle11g - Oracle 11 variable sensitivity of elapsed time to LINESIZE changes -


i've read documentation tuning sqlplus regarding linesize struggling work out why 1 set of oracle 11 servers seems behave differently set of oracle 11 servers respect linesize

running following queries gives me 'strange' elapsed time variation.

select object_name dba_objects rownum < 140000;

1.1. sqlplus on sensitive servers

100   00:00:04.28 00:00:04.18 00:00:04.04 1000  00:00:06.48 00:00:06.37 00:00:06.32 10000 00:00:39.98 00:00:40.17 00:00:39.78

1.2. sqlplus on non-sensitive servers

100   00:00:04.90 00:00:04.93 00:00:04.77 1000  00:00:04.91 00:00:05.18 00:00:04.90 10000 00:00:05.79 00:00:05.54 00:00:05.74

select owner, object_name dba_objects rownum < 140000;

2.1. sqlplus on sensitive servers

100   00:00:06.65 00:00:07.53 00:00:06.88 1000  00:00:07.84 00:00:08.27 00:00:08.24 10000 00:00:40.71 00:00:41.54 00:00:40.60

2.2. sqlplus on non-sensitive servers

100   00:00:07.91 00:00:07.15 00:00:07.69 1000  00:00:05.64 00:00:05.59 00:00:05.52 10000 00:00:06.27 00:00:06.37 00:00:06.34

the variable changed in running these queries linesize setting. repeatedly ran same query linesize set 100, 1000, 10000.

my main question is: why 1 set of servers seemingly more sensitive changing linesize other set. sensitive servers range 4s 40s, non-sensitive ones range range 4s 7s.

what explain difference in 'sensititivity' ?

looking @ 2.2 numbers, see variability induced "linesize small", larger linesize results in lower elapsed time (going 100 1000). why same effect not visible in 2.1 numbers.

note:

  • identical sqlplus clients used identical settings reported show all.

  • oracle stats returned autotrace virtually identical (no order of magnitude variations)

  • oracle database 11g enterprise edition release 11.2.0.3.0 - 64bit production

finally got bottom of irksome problem.

the version of sqlplus client we're using is: sql*plus: release 10.2.0.3.0 - production

the setting separated 'sensitive' 'non-sensitive' sqlplus hosts nls_lang environment variable. on non-sensitive ones variable not set , defaults american_america.us7ascii on sensitive ones variable set american_america.utf8

once know , following links appear: https://community.oracle.com/thread/979446?tstart=0


-

Comments

Post a Comment

Popular posts from this blog

PySide and Qt Properties: Connecting signals from Python to QML -

i trying run simple pyside appliccation design made in qml. call function in qml python in separated thread. i have following qml view: import qt 4.7 rectangle { visible: true width: 100; height: 100 color: "lightgrey" text { id: datestr objectname: "datestr" x: 10 y: 10 text: "init text" font.pixelsize: 12 function updatedata(text) { datestr.text = qstr(text) console.log("you said: " + text) } } } here application: some imports.... #!/usr/bin/python import sys import time pyside import qtdeclarative, qtcore pyside.qtgui import qapplication pyside.qtdeclarative import qdeclarativeview the qthread worker.... #worker thread class worker(qtcore.qthread): updateprogress = qtcore.signal(int) def __init__(self, child): qtcore.qthread.__init__(self) self.child = child def run(self):
Read more

c# - DevExpress.Wpf.Grid.InfiniteGridSizeException was unhandled -

Image
when using devexpress, see error: devexpress.wpf.grid.infinitegridsizeexception unhandled message="by default, infinite grid height not allowed since grid rows rendered , hence grid work slowly. fix issue, should place grid container give finite height grid, or should manually specify grid's height or maxheight. note can avoid exception setting gridcontrol.allowinfinitegridsize static property true, in case grid run slowly." the problem dxgrid has infinite height. to fix, set height non-infinite. snoop absolutely invaluable this: if "height" xaml element infinite (i.e. 0 or nan ), can set using one of following: option 1: height="{binding path=actualheight, relativesource={relativesource mode=findancestor, ancestortype=uielement}}" option 2: verticalalignment="stretch" option 3: height="auto" hint: use verticalalignment="stretch" if child of grid <rowdefinition height=
Read more

scala - 'wrong top statement declaration' when using slick in IntelliJ -

Image
i'm porting project scala 2.9 2.10, therefore have use slick instead of scalaquery. i'm using slick 2.1.0 since supports ms access. according this tutorial , upgrade guide changed robs object class , added val robs : why error message wrong top statement declaration , how rid of it? edit: i'm new scala... according this question seems can't put val outside of methods or classes, right? code above directly in packge. right approach slick then? should move code in class or trait? according this changed val robs = tablequery[robs] to object robs extends tablequery(new robs(_)) {} . no warnings or errors anymore. :)
Read more