[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | MS Windows NT Developers |
Notice: | See note 1222 for MS bug reporting info |
Moderator: | TARKIN::LIN EIBER |
|
Created: | Mon Nov 11 1991 |
Last Modified: | Tue Jun 03 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 3247 |
Total number of notes: | 15633 |
3214.0. "MS/RPC vs. MS/LRPC performance?" by GUIDUK::BARTLETT () Wed Mar 26 1997 13:16
I'm working on an application that uses MS/RPC for interprocess
communication between a handful (4) NT service modules. I have a
question about performance differences between RPC calls between
client and server running on the same system and client and server
running on separate systems.
From limited experience with DCE/RPC on unix systems, I know that
early versions of OSF/DCE had a problem with RPC calls (bindings
particularly) taking longer when communicating with a server on
the same system as the client than the same calls would take over
a network interface.
My question is whether MS/RPC is intelligent enough to keep data
transfers above the transport layer if the client communicates
with the server on the same system. I think that recent versions
of OSF/DCE do this and long as you don't specify the full network
path on the binding request.
This kind of information is helpful since, otherwise I'd have to
do some testing to determine whether there are major performance
differences between local RPC and remote RPC. If there is a
substantial difference, I'll probably end up writing conditional
code to check for local or remote access and use LRPC for local
and RPC for remote communications.
Thanks,
Roger Bartlett.
T.R | Title | User | Personal Name | Date | Lines
|
---|