Oracle Trace Analyzer
From: Mladen Gogala <gogala.mladen_at_gmail.com>
Date: Thu, 3 Jan 2013 19:28:38 +0000 (UTC)
Message-ID: <pan.2013.01.03.19.28.30_at_gmail.com>
I've just learned from the author that the venerable TRCA package uses just PL/SQL to parse the trace files. That's why it's so slow and resource consuming tkprof, orasrp and Cary's Method R profiler. There are many parsing good tools but PL/SQL is not one of them. Most of the parsing tools use finite automata which require lexer and grammar. Lexer identifies the tokens while the grammar part performs the required actions with the tokens. The most frequently used parsing tools are lex/ yacc (flex/bison) and Perl.
That is why parsing of a 30MB trace file takes 10 minutes with TRCA and it takes seconds with tkprof or orasrp.
Date: Thu, 3 Jan 2013 19:28:38 +0000 (UTC)
Message-ID: <pan.2013.01.03.19.28.30_at_gmail.com>
I've just learned from the author that the venerable TRCA package uses just PL/SQL to parse the trace files. That's why it's so slow and resource consuming tkprof, orasrp and Cary's Method R profiler. There are many parsing good tools but PL/SQL is not one of them. Most of the parsing tools use finite automata which require lexer and grammar. Lexer identifies the tokens while the grammar part performs the required actions with the tokens. The most frequently used parsing tools are lex/ yacc (flex/bison) and Perl.
That is why parsing of a 30MB trace file takes 10 minutes with TRCA and it takes seconds with tkprof or orasrp.
-- Mladen Gogala The Oracle Whisperer http://mgogala.byethost5.comReceived on Thu Jan 03 2013 - 20:28:38 CET