We have three ways to see execution related timings
irdb.log file in the main IRDB directory gives a record of the queries that are executed, and a breakdown of the major times of execution that went into the query. If you stop the service net stop “irdb server” , you should then be able to launch irdbServer.exe in console mode, and see the output, when you connect to the server. You will then see the execution times dynamically as your queries are run. Don’t forget to run net start “irdb server”, when you are finished.
If you are in irdb_query, and connect to the server, if you execute the following command
set query_log = 1000
It will remember the last 1000 commands. You can then run the sql command select * from information_schema.query_log and it will return execution time of the most recent queries, and some other stats. select * from information_schema.query_log_delta will reset the log after, and only give you the incremental queries. This is useful, if you want to build a monitoring tool
3. TIMINGS command in irdbImport
Inside irdbImport if you run the command TIMINGS , it will display some cumulative timing information about the irdbImport program.