The efficiency of oci program with OCI_COMMIT_ON_SUCCESS

Question

I have write a demo program to insert 1000 row data into a tab.
As I want to commit at every insert operation, I call OCIStmtExecute with OCI_COMMIT_ON_SUCCESS parameter.
And the time cost for each row is between 5ms and 10 ms.
At the same time, insert data using SQL:
declare
return_res number(4);
aa1 varchar(15);
aa2 varchar(150);
aa3 varchar(150);
aa4 varchar(150);
aa5 varchar(150);
aa6 varchar(150);
begin
for i in 1..1000 loop
aa1 := '13900000001';
aa2 := '000102030405060708090a0b0c0d0e0f';
aa3 := '000102030405060708090a0b0c0d0e0f';
aa4 := '000102030405060708090a0b0c0d0e0f';
aa5 := '000102030405060708090a0b0c0d0e0f';
aa6 := '000102030405060708090a0b0c0d0e0f';
insert into avinfotab_3g1 values(i,aa1,aa2,aa3,aa4,aa5,aa6);
commit;
select count(*) into return_res from avinfotab_3g1;
delete from avinfotab_3g1 where strsImsi = '13900000001';
commit;
end loop;
end;
result:
Command was executed successfully
Executed: 6/2/09 4:10:27 PM CST Execution: 922/ms
It's cost less than 1ms per row.
Why the OCI program's efficiency so low?
Edited by: bigtreefxs on 2009-6-2 下午11:06
Edited by: bigtreefxs on 2009-6-2 下午11:08

Answer 1

As wel the commit in the pl/sql block is executed as part of one pl/block executed on the server.
If you do the execute in oci from a client app, you have as many roundtrips as execution...