PowerBuilder applications that perform well today in your local network may not perform well in a distributed architecture tomorrow. Likewise, typical PowerBuilder development practices may not be suitable for a distributed architecture. The several techniques outlined in this guide are intended to steer you in general directions. It is recommended to extrapolate from these examples and apply to your particular situation. Please keep in mind that excessive server calls is the single biggest culprit of performance issues over the Internet, which is a relatively high latency connection.

Purchasing expensive network connectivity and faster hardware can make up for suboptimal code. Sometimes the cost of doing this is less than the cost of optimizing the code. If you do take this route, keep in mind that a low-latency network connection is generally the key rather than a high-bandwidth connection. Reason being, for most PowerBuilder applications and deployments, it is the network latency that kills the runtime performance not bandwidth limitations.