Re: Increasing CPU on every execution of an anonymous block sent from WebLogic
- From: "Alberto Dell'Era" <alberto.dellera@xxxxxxxxx>
- To: paul.baumgartel@xxxxxxxxxxxxxxxxx
- Date: Tue, 20 Mar 2007 20:51:33 +0100
> Analysis of the trace files for the bind-variable version reveals that the
CPU time to EXEC the anonymous block (and, to a lesser extent, its
constituent INSERT statements) steadily increases. The first time through
the CPU time is about 0.02 second. By the last execution before the
timeout, the CPU time is just about 1.0 second. Interestingly, the logical
I/O stats for each execution are quite low (<100 current reads and
consistent reads) and quite consistent.
Are those timings for a serial execution of the block by
the same connection, or by concurrent execution by different
connections ?
Is the block identical for bind variables names also ? ie
begin
insert ... values (:bind_one);
insert ... values (:bind_one);
end;
or
begin
insert ... values (:bind_one);
insert ... values (:bind_TWO);
end;
--
Alberto Dell'Era
"dulce bellum inexpertis"
--
http://www.freelists.org/webpage/oracle-l
- References:
- Increasing CPU on every execution of an anonymous block sent from WebLogic
- From: Baumgartel, Paul
Other related posts:
- » Increasing CPU on every execution of an anonymous block sent from WebLogic
- » RE: Increasing CPU on every execution of an anonymous block sent from WebLogic
- » RE: Increasing CPU on every execution of an anonymous block sent from WebLogic
- » RE: Increasing CPU on every execution of an anonymous block sent from WebLogic
- » RE: Increasing CPU on every execution of an anonymous block sent from WebLogic
- » RE: Increasing CPU on every execution of an anonymous block sent from WebLogic
- » Re: Increasing CPU on every execution of an anonymous block sent from WebLogic
- » Re: Increasing CPU on every execution of an anonymous block sent from WebLogic
- » Re: Increasing CPU on every execution of an anonymous block sent from WebLogic
- » RE: Increasing CPU on every execution of an anonymous block sent from WebLogic
- » RE: Increasing CPU on every execution of an anonymous block sent from WebLogic
- » RE: Increasing CPU on every execution of an anonymous block sent from WebLogic
- » RE: Increasing CPU on every execution of an anonymous block sent from WebLogic
- » RE: Increasing CPU on every execution of an anonymous block sent from WebLogic
- » RE: Increasing CPU on every execution of an anonymous block sent from WebLogic
- » RE: Increasing CPU on every execution of an anonymous block sent from WebLogic
- » RE: Increasing CPU on every execution of an anonymous block sent from WebLogic
- » RE: Increasing CPU on every execution of an anonymous block sent from WebLogic
- » RE: Increasing CPU on every execution of an anonymous block sent from WebLogic
- » Re: Increasing CPU on every execution of an anonymous block sent from WebLogic
- » RE: Increasing CPU on every execution of an anonymous block sent from WebLogic
- » Re: Increasing CPU on every execution of an anonymous block sent from WebLogic
- » Re: Increasing CPU on every execution of an anonymous block sent from WebLogic
CPU time to EXEC the anonymous block (and, to a lesser extent, its constituent INSERT statements) steadily increases. The first time through the CPU time is about 0.02 second. By the last execution before the timeout, the CPU time is just about 1.0 second. Interestingly, the logical I/O stats for each execution are quite low (<100 current reads and consistent reads) and quite consistent.
- Increasing CPU on every execution of an anonymous block sent from WebLogic
- From: Baumgartel, Paul