[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Use COM for shell extension / TSVNCache communication

From: Ivan Zhakov <chemodax_at_gmail.com>
Date: Thu, 24 Mar 2016 21:24:23 +0300

On 24 March 2016 at 20:48, Stefan Küng <tortoisesvn_at_gmail.com> wrote:
> On 24.03.2016 07:42, Ivan Zhakov wrote:
>> Hi,
>>
>> Currently Tortoise shell extension uses named pipes for communicating
>> with TSVNCache.exe. I'm considering to change this to use COM for
>> inter-process communication. This should improve performance and
>> concurrency.
>
> Are you sure that COM is faster than a simple pipe? From my experience I
> found COM to be slower. Of course my last attempts at this were five
> years ago so things might have changed...
>
COM performance didn't change significantly in the past five years.
But I expect COM to be faster for several reasons:
1. COM uses LRPC for communication which extremely fast. It uses
shared memory and NDR/NDR64 for marshaling data.
2. Free-threaded COM server uses thread-pool to execute interface methods.
3. There is no ERROR_PIPE_BUSY race condition between client connected
to the pipe and server created new pipe.
4. The client may call interface methods concurrently from different
threads without using mutex.

There some overhead of using COM, but the transport itself should be
faster. Btw how did you measure performance? Did you use typelibrary
based marshaller or registered separate proxy dll? What threading
model did you use for COM server in your tests?

-- 
Ivan Zhakov
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=3167128
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2016-03-24 19:25:19 CET

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.