Overhead for calling a procedure / function in another Oracle package

Question

We discuss the impact of performance on placing a common function / procedure in a separate package or using a local copy in each package.

My thinking is that it would be cleaner to have common code in the package, but others are worried about the workload.

Thoughts / experience?

Answer 1

Put it in one place and call it out of many - reusing this base code. Any overhead when calling one package from another will be negligible. If they still doubt it, ask them to demonstrate the difference in performance.

Answer 2

, , . .

.

.

Answer 3

, , .

, , . , " Oracle". , . , , Oracle. - , .

. Oracle : spec body: Spec - , ( ). - . , 2 .

Oracle , , VALID INVALID. , , . , A, B, , A, A B. Oracle , , B. , B , ( ).

. , Oracle .

, A B . B. , , Oracle , , B, .

B, Oracle , , , - ( B A ). , Oracle , , timestemp. , , .

, , , . , Oracle .

, . Oracle. . :

• , . , , . - "" , A B B A. , .

• Store the package specification and package body in separate source files. And if you only need to change the body, do not touch the specification!