If I use DBMS_Profiler to profile a long running (5 hour) PL/SQL script, how much longer should I expect the script to run with profiling? I realize this will be dependent on what the script is doing, but in general am I looking at seconds, minutes, or perhaps more?
- Anybody can ask a question
- Anybody can answer
- The best answers are voted up and rise to the top
I have used DBMS_PROFILER on 9i and 10g a bit. Depending on the code I have seen between 2% and 10% time penalty for profiling.
Luckily the profiler was built to cache results in memory and flush to disk infrequently. I think it depends more on number of lines executed rather than the total wall clock time of the profiler - since that is what the profiler is watching anyway.
The best way to find out will be to run some known code samples with and without using the profiler. The differences normally should not be much but indeed can vary. Even dbms_application_info can hurt when put inside a high frequent loop.