Begin f(p= :1 ); commit; end;

Question

I was doing some tuning of my Oracle instance running Apex this morning, and the above text is the top by elapsed time, CPU time, and user wait time (with ~4500 executions in the past three days). It's not my SQL. By the look of it, it's probably a commit being performed by Apex itself. I'd just like to have an idea if that's what it is, if it's normal for it to be relatively expensive overal SQL operation, if there's any resource I can give that will make it faster, etc.

Answer 1

matthew_morris wrote:
I was doing some tuning of my Oracle instance running Apex this morning, and the above text is the top by elapsed time, CPU time, and user wait time (with ~4500 executions in the past three days). It's not my SQL. By the look of it, it's probably a commit being performed by Apex itself. I'd just like to have an idea if that's what it is"f" is the name of the procedure Apex uses to process page requests. It maps onto the URL you'll see when you load up an apex page e.g.:
   http://myapexdomain/apex/f?p=4500:1000which happens to be URL for the Application Editor Interface...
if it's normal for it to be relatively expensive overal SQL operationIt depends on what your page(s) does when it loads. If there's particularly arduous page processing being done (e.g. a complex report query), then it naturally follows that the call to "f" will take a longer time to execute.
if there's any resource I can give that will make it faster, etc.See above - the best thing to do is see what page(s) in your application(s) take the longest to run (making judicious use of "debug" mode to identify the bottlenecks) and apply your tuning efforts there.