If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > Database Server Software > DB2 > db2batch

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 06-14-07, 19:02
timtim10 timtim10 is offline
Registered User
 
Join Date: Jun 2007
Posts: 5
db2batch

Hi, I am using db2batch to measure my queries but always the elapsed time is wrong. E. g. the query runs about 10 seconds but db2batch measures about 100 seconds. Does anybody have the same problem or does anybody have a clue?
I am using DB2 Express 9.1.2 with Windows XP
Reply With Quote
  #2 (permalink)  
Old 06-17-07, 06:06
timtim10 timtim10 is offline
Registered User
 
Join Date: Jun 2007
Posts: 5
Isn't there anybode who has the same problem or knows what to do?
Reply With Quote
  #3 (permalink)  
Old 06-25-07, 05:54
stolze stolze is offline
Registered User
 
Join Date: Jan 2007
Location: Jena, Germany
Posts: 2,662
Could you let us know a bit more about your scenario? What's the query, what's the exact output of db2batch, what's the result of the "time" command?
__________________
Knut Stolze
IBM DB2 Analytics Accelerator
IBM Germany Research & Development
Reply With Quote
  #4 (permalink)  
Old 06-27-07, 06:27
timtim10 timtim10 is offline
Registered User
 
Join Date: Jun 2007
Posts: 5
Hi, here a little bit more:

My db2batch command looks like:

db2batch -d CDDB -f test.sql -r ausgabe.txt -o e 2 r 10 p 1 -v on -s on


-------------------------------------------------------------
* Zeitmarke: Wed Jun 27 2007 12:19:57 Westeuropäische Normalzeit
---------------------------------------------


* SQL-Anweisung Nummer 1:


select *

from artists art1, song, albums alb, artist2album art2, cds, cdtracks cdt

where art2.artistid=art1.artistid and art2.albumid=alb.albumid and

art2.artist2albumid=cds.artist2albumid and song.songid=cdt.songid and cdt.cdid=cds.cdid;

Typ Anzahl Wiederholungen Gesamtzeit (S) Mindestzeit (S) Maximalzeit (S) Arithmetisches Mittel Geometrisches Mittel Abgerufene Zeile(n) Ausgegebene Zeile(n)

--------- ----------- -------------- -------------- --------------- --------------- --------------------- -------------------- ------------------- --------------------

Anweisung 1 1 126,334136 126,334136 126,334136 126,334136 126,334136 1163691 100


* Gesamtanzahl Einträge: 1
* Gesamtzeit: 126,334136 Sekunden
* Mindestzeit: 126,334136 Sekunden
* Maximalzeit: 126,334136 Sekunden
* Zeit (arithmetisches Mittel): 126,334136 Sekunden
* Zeit (geometrisches Mittel): 126,334136 Sekunden
---------------------------------------------

* Zeitmarke: Mi Jun 27 2007 12:20:20 Westeuropäische Normalzeit

-------------------------------------------------

When I compare the timestamps I think the query takes about 23 seconds.
But db2batch says that the query takes about 126 seconds.
Reply With Quote
  #5 (permalink)  
Old 06-29-07, 03:46
stolze stolze is offline
Registered User
 
Join Date: Jan 2007
Location: Jena, Germany
Posts: 2,662
Interesting... I have never seen that before. Still, how long does db2batch run in total, i.e. what's the output of the Unix command "time"?

As another recommendation you may want to use the switch "-i complete" as well for db2batch.
__________________
Knut Stolze
IBM DB2 Analytics Accelerator
IBM Germany Research & Development
Reply With Quote
  #6 (permalink)  
Old 06-29-07, 07:10
timtim10 timtim10 is offline
Registered User
 
Join Date: Jun 2007
Posts: 5
Hi, I'm using Windows XP and this is the output for one of my queries. db2batch measures 122 seconds, but as you can see the total elapsed time for executing the command was TotalSeconds : 23,8681251

* Abgelaufene Zeit: 122,714462 Sekunden

---------------------------------------------
* Zeitmarke: Fr Jun 29 2007 13:05:24 Westeuropäische Normalzeit


Days : 0
Hours : 0
Minutes : 0
Seconds : 23
Milliseconds : 868
Ticks : 238681251
TotalDays : 0,000276251447916667
TotalHours : 0,00663003475
TotalMinutes : 0,397802085
TotalSeconds : 23,8681251
TotalMilliseconds : 23868,1251

With -i complete:

* Vorbereitungszeit: 1,972228 Sekunden
* Ausführungszeit: 139,029307 Sekunden
* Abrufzeit: 0,025864 Sekunden
* Abgelaufene Zeit: 141,027400 Sekunden (gesamt)

---------------------------------------------
* Zeitmarke: Fr Jun 29 2007 13:08:51 Westeuropäische Normalzeit


Days : 0
Hours : 0
Minutes : 0
Seconds : 27
Milliseconds : 23
Ticks : 270232487
TotalDays : 0,000312769082175926
TotalHours : 0,00750645797222222
TotalMinutes : 0,450387478333333
TotalSeconds : 27,0232487
TotalMilliseconds : 27023,2487

Something is wrong with the execution time, but I have no clue
Reply With Quote
  #7 (permalink)  
Old 06-29-07, 15:24
stolze stolze is offline
Registered User
 
Join Date: Jan 2007
Location: Jena, Germany
Posts: 2,662
You may want to open a PMR with IBM support to get this resolved. I don't think there is anything we can do here.

p.s: I'm still not sure if the execution of your script in "db2batch" was completed within 22 seconds real time. Did you use a regular wrist watch or something to double-check that?
__________________
Knut Stolze
IBM DB2 Analytics Accelerator
IBM Germany Research & Development
Reply With Quote
  #8 (permalink)  
Old 07-09-07, 15:44
timtim10 timtim10 is offline
Registered User
 
Join Date: Jun 2007
Posts: 5
Yes, I checked the execution time with a wrist watch too.
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On