Performance statistics 
Author Message
 Performance statistics

We have a number of systems in a client/server configuration on
a Lan. Several of the systems are at remote sites connected via
WAN bridges. I have been tasked with producing some statistics
to see what benefit (if any) we would get from upgrading the speed
of the comms lines to the remote sites. I started to do this and
have created a test database agaist which I will run benchmark
queries. ( The system is strictly 9:00AM to 5:00PM so provided I
run the tests out of hours they will not be affected by other use
of the database). The DBA suggested that I use the option

        export II_EMBED_SET="printqry"

at the shell level. This causes statistics to be written to a
file "iiprtqry.log"

On the remote client the first of my queries runs for around 3-4
minutes elapsed. However the output in iiprtqrt.log looks like this:-

Query text:
   select * from dgh_test
Query Send Time:       Thu Dec  2 18:44:36 1993
Query Response Time:   Thu Dec  2 18:44:36 1993
Response CPU Time:     210
Qry End CPU Time:      5218

How should I interpret this ?. Is the Query response time when the first
result row is sent back ? Would I be better off using ESQL and doing my
timings in "C".
--



Tue, 21 May 1996 19:31:43 GMT
 Performance statistics


: We have a number of systems in a client/server configuration on
: a Lan. Several of the systems are at remote sites connected via
: WAN bridges. I have been tasked with producing some statistics
: to see what benefit (if any) we would get from upgrading the speed
: of the comms lines to the remote sites. I started to do this and
: have created a test database agaist which I will run benchmark
: queries. ( The system is strictly 9:00AM to 5:00PM so provided I
: run the tests out of hours they will not be affected by other use
: of the database). The DBA suggested that I use the option

:       export II_EMBED_SET="printqry"

: at the shell level. This causes statistics to be written to a
: file "iiprtqry.log"

: On the remote client the first of my queries runs for around 3-4
: minutes elapsed. However the output in iiprtqrt.log looks like this:-

: Query text:
:    select * from dgh_test
: Query Send Time:       Thu Dec  2 18:44:36 1993
: Query Response Time:   Thu Dec  2 18:44:36 1993
: Response CPU Time:     210
: Qry End CPU Time:      5218

: How should I interpret this ?. Is the Query response time when the first
: result row is sent back ? Would I be better off using ESQL and doing my
: timings in "C".
: --

Hi Dave,

This may or may not help but... I've noticed that long queries get logged
twice when I use iiprtqry.log, the second time the time details are correct.
Or they *look* more plausible anyway.

I guess it's a bug!

Angela

--
I don't believe any of this and neither does my employer...
--
        Angela Lamb                     Phone:  0344-472301
        ICL Client-Server Systems               +44-344-472301
        Lovelace Rd

        Berks  RG12 8SN
        UK
--
life's an illusion / love is a dream
but i don't know / why it is...  everybody's happy nowadays     (Shelley)
--



Tue, 21 May 1996 21:04:42 GMT
 
 [ 2 post ] 

 Relevant Pages 

1. Performance Statistics

2. Making Sense of Performance Statistics

3. SqL performance statistics

4. BCP Performance statistics to output file

5. BCP Performance statistics to output file

6. Performance statistics empty: data overflow

7. Performance Statistics collection in Oracle

8. Performance statistics related to listener.get_cmd

9. alert_SID.log :Performance statistics empty: data overflow

10. Performance statistics

11. Sybase performance statistics


 
Powered by phpBB® Forum Software