From "Strategies for reducing Notes/Domino network bandwidth requirements � how IBM does it," by John Lamb, which originally appeared in the January/February 2000 edition of The View, http://www.eview.com.
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
Analyzing the RPC traffic between the client and server can help to answer performance issues on server-based applications. There are at least three reasons to strive to eliminate RPC calls.
-They contribute to perceived response time.
-Each call is subject to network delays and failure.
-Each RPC generates load on the network and on the server.
Take the time to analyze the RPC traffic generated by your applications to ensure that you are making efficient use of network and server resources. On Lotus Notes clients R4.5 and higher for Windows 95 or 98, you can use an undocumented (and therefore non-supported) feature of the Notes client to track RPC activity. Add the following three entries to your NOTES.INI file:
(e.g. Filename=Ndebug.txt which will be created in your Notes directory)
The Debug_Outfile entry (which is optional) will direct RPC log output to the filename specified.
When you bring up Notes with these added entries, new windows showing Notes activities will open. When you access a remote database, the debug window showing RPC commands will open. The debug window corresponds to the information that will be written to the Debug_Outfile log file you specified. Here is the format of the entries in the windows and log file.
(sequential number), RPC_NAME, time to complete, [bytes_sent+bytes_received=total]
To remove RPC monitoring, do not close the debug windows manually (they close when you exit Notes). Remove the statements you added to the INI files, and restart Notes.