Reducing the Number of RPCs

Remote procedure calls (RPCs) allow two processes to communicate transparently over a network. Although RPCs are essential to client-server architecture, they can cause significant network overhead. When a message is sent, it is enclosed within an envelope of information that is required for addressing, routing, and network protocol. This extra information and the time required to process it is called functional overhead. For example:

• Depending on the operation, the functional overhead of an RPC is at least 10 milliseconds, plus an average of 200 milliseconds for a round trip from the client to the server.
• Each RPC expends an average of 300 bytes of network I/O overhead, as well as server and client CPU overhead for sending, receiving, and processing.
• When direct binding of messages is possible (such as when TCP-IP protocols or IPX protocols are used), each RPC causes only an average of 260 bytes of network overhead.

An excessive number of RPCs leaves the server with less time to process internal requests, which affects the server’s performance and scalability. Minimizing the number of RPCs for your application improves response time for clients, and also improves the server’s overall performance.

    To reduce the number of RPCs

• Use the IMAPIProp::GetProps and IMAPIProp::SetProps methods efficiently by batching calls to these methods. See Getting and Setting Properties Efficiently and Minimizing IStream Interface Use.
• Use the MAPI_DEFERRED_ERRORS flag, which has the secondary effect of delaying calls until the information is needed. See Using the MAPI_DEFERRED_ERRORS Flag.
• When possible, access data locally by keeping frequently used items cached at the client and by using properties that are already stored locally. See Accessing Data Locally and Building a Cache of Frequently Used Items.
• Choose the MAPI method that uses the fewest RPCs. See Selecting MAPI Methods That Use Fewer RPCs.