Dynamic delinkage of libraries is a complex and costly operation. Excessive use of this capability can lead to severe, system-wide performance problems. The more services a program uses simultaneously (including open subports and open databases), the costlier delinking gets. In addition, the larger a process family is, the more costly library delinkages are. Exiting an environment containing and using a library declaration causes a dynamic delink. Application designers should ensure all libraries are declared globally, and that dynamic delinkage is avoided when unnecessary to the application design.