Hi,
I am using the progress profiler to improve the performance duringxml-parsing. But the information I get from the profiler is incomplete.
I have the following situation:
Prg. A looks for files in a directory and calls a procedure in B for every file
found
Prg. B creates a SAX-PARSER object and sets Prg. C as callback
(SAX-PARSER:HANDLER)
Prg. C stores data during the parse and calls a procedure in persistent
procedure Prg. D for every block in XML-File (during my run every
file contains just one block)
Prg. D validates values and stores data to DB, calls some helper functions
in persistent procedure Prg. E by the way
Prg. E contains some helper functions
The persistent procedures Prg. C and Prg. D are loaded by Prg. A.
My first attempt was to start and stop the profiler in Prg. A, start itwith the 3rd file found, and stop it after about 15 files have beenprocessed.
That leaves me with a profile that shows me times of what happend in A,some procedures in Prg. E, but nothing of the main processing in Prg. Cand Prg. D.
So I moved starting/stopping of the profiler to Prg. C. Then I got thetimes of Prg. D and Prg. E, but I didn't get times and listing of Prg.C! And because of the "late start" I don't have anything on Prg. A andPrg. B so this doesn't help much.
Another issue is that even if the profiler is started in Prg. A andthen B/C/D are called 15 times, the profiler shows calls to functionwhich have to be executed at least once for every file, with acall-number of "1" (procedures in Prg. E as there is nothing inbetween).
Btw.: Sometimes I get just the linenumbers with execution times butwithout the codelines themselves - but that's not that bad because theline numbers are the same as they are in a compile with debug-list.
So has anybody experienced similar effects or does anyone know how toget around this and get a complete result with times of all procedures?
I'd really appreciate any answer. Thanks in advance!
Karl Rieser
I am using the progress profiler to improve the performance duringxml-parsing. But the information I get from the profiler is incomplete.
I have the following situation:
Prg. A looks for files in a directory and calls a procedure in B for every file
found
Prg. B creates a SAX-PARSER object and sets Prg. C as callback
(SAX-PARSER:HANDLER)
Prg. C stores data during the parse and calls a procedure in persistent
procedure Prg. D for every block in XML-File (during my run every
file contains just one block)
Prg. D validates values and stores data to DB, calls some helper functions
in persistent procedure Prg. E by the way
Prg. E contains some helper functions
The persistent procedures Prg. C and Prg. D are loaded by Prg. A.
My first attempt was to start and stop the profiler in Prg. A, start itwith the 3rd file found, and stop it after about 15 files have beenprocessed.
That leaves me with a profile that shows me times of what happend in A,some procedures in Prg. E, but nothing of the main processing in Prg. Cand Prg. D.
So I moved starting/stopping of the profiler to Prg. C. Then I got thetimes of Prg. D and Prg. E, but I didn't get times and listing of Prg.C! And because of the "late start" I don't have anything on Prg. A andPrg. B so this doesn't help much.
Another issue is that even if the profiler is started in Prg. A andthen B/C/D are called 15 times, the profiler shows calls to functionwhich have to be executed at least once for every file, with acall-number of "1" (procedures in Prg. E as there is nothing inbetween).
Btw.: Sometimes I get just the linenumbers with execution times butwithout the codelines themselves - but that's not that bad because theline numbers are the same as they are in a compile with debug-list.
So has anybody experienced similar effects or does anyone know how toget around this and get a complete result with times of all procedures?
I'd really appreciate any answer. Thanks in advance!
Karl Rieser