Tuesday, September 14, 2010

performance of tkprof vs orasrp

Usually tkprof is faster than orasrp. But there are some cases when tkprof processes trace file slower than orasrp. Take for example today's situation.

1.7Gb trace file with about 16 thousands of different statements. Total number of calls is about 10 millions (although, it doesn't matter). OraSRP processed this file for 3 minutes. Tkprof for HP-UX processed it for 5 minutes. Tkprof for Linux consumed 1.5Gb of virtual memory and didn't finish in an hour.

The source of the problem lies in the big number of statements. When the number of statements in trace file is more than, say, 10 thousands, tkprof performs worse than orasrp and may even stuck.

Labels: ,

6 Comments:

Blogger Mark Bobak said...

Hi Egor,

I have a trace file over 3.5GB in size. When I tried to run ORASrp against it, (on Windows), I got "Error: Out of memory".

Any suggestions?

3:00 AM  
Blogger egor said...

@Mark
> I got "Error: Out of memory".

Need some additional info.
What version (orasrp --version)?
Have you got this error immediately after orasrp start-up or after some work?
Would you please to try to run 'orasrp --binds=0 ...' (this way you disable processing of binds data) and tell me whether it runs successful?

12:09 PM  
Blogger Timur Akhmadeev said...

Hi Egor,

it looks like Statement Objects Statistics is correctly displayed in the text report version only. HTML version lacks Object IDs/names in it. Session Objects Statistics is OK in the HTML report.

3:46 PM  
Blogger egor said...

@Timur

Sorry, fixed.

12:04 AM  
Blogger Timur Akhmadeev said...

@Egor

don't be sorry :)
Thank you for this wonderful tool.

5:13 PM  
Blogger Alexey Besedin said...

Hello!
I've tried to analyze 15Gb trace file using orasrp tool but got an error: Out of memory.

When I started the process again I found that orasrp constantly consumes RAM anf it does not matter whether I using text or html mode.

Additional info:
Win8 x64
orasrp x32

12:08 PM  

Post a Comment

<< Home