Oracle Call Interface Programmer's Guide Release 8.1.5 A67846-01 |
|
This appendix provides information about server roundtrips incurred during various OCI calls. This information can be useful to programmers when determining the most efficient way to accomplish a particular task in an application.
The appendix contains the following sections:
This appendix provides information about server roundtrips incurred during various OCI calls. This information can be useful when determining the most efficient way to accomplish a particular task in an application.
The number of server round trips required by OCI relational functions are listed in Table C-1:
Function | # of Server Roundtrips |
---|---|
OCIStmtGetPieceInfo() |
1 |
OCIStmtSetPieceInfo() |
1 |
Table C-2 lists the server roundtrips incurred by the OCILob*() calls. Information about the read and write calls is listed after the table.
The number of roundtrips required depends on how the call is used:
The number of roundtrips required depends on how the call is used:
Table C-3 lists the number of server round trips required for the object and cache functions. These values assume the cache is in a warm state, meaning that the type descriptor objects required by the application have been loaded.
The number of server round trips required by OCIDescribeAny(), OCIAttrGet(), and OCIParamGet() are listed in Table C-4:
The number of round trips for the datatype mapping and manipulation functions are listed in Table C-5. The asterisks in the table indicate that all functions with a particular prefix incur the same number of server roundtrips. For example, OCINumberAdd(), OCINumberPower(), and OCINumberFromText() all incur zero server roundtrips.
The functions listed in Table C-6 are local and do not require a server roundtrip: