I need to provide a C++ application as a service. Client of the service and the service can be on the same machine or distributed on different machines based on the load. This application takes a ~2KB string as input and returns almost similar size of string after some processing. Turnaround time for the client should be really quick. What is the best mechanism to implement this?
+4
A:
Given that the input size is less than a memory page wide on localhost, it's unlikely that any mechanism is going to make a measurable difference here. As for remote machines, network latency will probably be the bottleneck rather than client/server issues.
Billy ONeal
2010-04-28 14:51:41
I was thinking to use HTTP as RPC in case of different machines. On single machine I can have HTTP or shared memory. What will be performance impact of using HTTP vs Shared Memory on localhost?
sand
2010-04-28 15:00:37
@sand: I would guess little to none. But the only way to be sure is to profile it.
Billy ONeal
2010-04-28 15:50:20
I expect shared memory + semaphores will be significantly more performant that TCP (even over the loopback.) However, especially if you must *also* support the remote-server scenario, TCP may be "good enough" and save you implementing both TCP (for the remote scenario) and shmem+IPC (for the local scenario.)
vladr
2010-04-29 14:35:42