Tuning Oracle Net - Expert Oracle RAC Performance Diagnostics and Tuning - page 339

kswsgfntpt : Metrics for svc : RAPTEST
kswsgfntpt : svc / fgval / clbdelta / scount : RAPTEST / 14.5833/ 1277.6327 7
kswsgthr: calling kelr_get_local_threshold() svc:RAPTEST
kswsgfntpt : Metrics for svc : RAPTEST
kswsgfntpt : svc / fgval / clbdelta / scount : RAPTEST / 18.7500/ 643.0413 9
kswsgthr: calling kelr_get_local_threshold() svc:RAPTEST
kswsgfntpt : Metrics for svc : RAPTEST
kswsgfntpt : svc / fgval / clbdelta / scount : RAPTEST / 27.0833/ 324.2762 13
kswsgthr: calling kelr_get_local_threshold() svc:RAPTEST
kswsgfntpt : Metrics for svc : RAPTEST
kswsgfntpt : svc / fgval / clbdelta / scount : RAPTEST / 33.3333/ 163.8512 16
kswsgthr: calling kelr_get_local_threshold() svc:RAPTEST
kswsgfntpt : Metrics for svc : RAPTEST
kswsgfntpt : svc / fgval / clbdelta / scount : RAPTEST / 100.0000/ 82.8510 20
kswsgthr : calling kelr_get_local_threshold() svc:RAPTEST
kswsgfntpt : Metrics for svc : RAPTEST
kswsgfntpt : svc / fgval / clbdelta / scount : RAPTEST / 100.0000/ 50.0000 25
kswsgthr: calling kelr_get_local_threshold() svc:RAPTEST
kswsgfntpt : Metrics for svc : RAPTEST
kswsgfntpt : svc / fgval / clbdelta / scount : RAPTEST / 100.0000/ 50.0000 28
kswsgthr: calling kelr_get_local_threshold() svc:RAPTEST
kswsgfntpt : Metrics for svc : RAPTEST
kswsgfntpt : svc / fgval / clbdelta / scount : RAPTEST / 100.0000/ 50.0000 31
kswsgthr: calling kelr_get_local_threshold() svc:RAPTEST
There are two parts to the preceding output. The Oracle kernel makes the call to determine the threshold
definitions using “kelr_get_local_threshold” and is identified by “kswsgthr.” The line starting with “kswsgfntpt”
displays the value for the various stats.
The “svc” indicates the service name. In the trace output just shown, “RAPTEST” is the service name.
The “clbdelta” indicates the connection load balance percentage value currently utilized by the service RAPTEST
on that instance.
The “scount” indicates the number of sessions that have made connections using that service on the instance.
The output should be read using the following format for better understanding:
kswsgfntpt : svc / fgval / clbdelta / scount :
RAPTEST / 100.0000/ 50.0000 / 25
In the preceding output, there is 50 percent load balance, and 25 sessions are connected to the service RAPTEST.
Connection Throughput
All clients connect to the database to do one of two things: either to write ( INSERT ) or modify ( UPDATE ) data into
the database or to read ( SELECT ) data from the database. As discussed earlier, speed at which data is written to the
database or retrieved from the database is normally measured by response time. Apart from the speed at which data
can be retrieved from the database or written to the database, response time also depends on the speed and volume
of the data transmission between the client machines and the database servers. This situation becomes more obvious
when large volumes or blocks of data need to be transmitted between the client and the database. Applications
request data from the database in number of rows. This is driven by the settings on the application browser on
the number of rows that it would like to view and display. The actual number of rows that can be received by the
application is controlled by the array size or buffer size that can hold these rows. Tuning the array size or buffer size is
required to improve the overall response times of the operation.