Which is faster, remoting or object pooling (COM+)

[Walter Zydhek]

Which would be less resource instensive and faster?
A "hosted" remoting class or a class set up with object
pooling via Component Services?

-Walt Zydhek

 

[Marina]

Not sure about efficiency, but remoting is going to be a lot less hassle
then dealing with COM+. Why would you want to use it unless you had to?

 

[Cor]

Hi Walter,

A typical question for the newsgroup

microsoft.public.dotnet.framework.adonet

A lot of people there who can answer that

I hope this helps?

Cor

 

[Michael Giagnocavo [MVP]]

Hi Walter,

A typical question for the newsgroup

microsoft.public.dotnet.framework.adonet

A lot of people there who can answer that

Well, it's not connection pooling, so it's not really related directly to
ADO.NET.

With Component Services (COM+), you have all the overhead and hassle. As
well, I believe there are certain restrictions on your .NET class. That
said, I think COM+ will be faster, since you're not serializing to a wire
format, but just doing in-memory marshalling, and that should be faster.
Unless you're 100% sure that you need every scrap of performance, and that
your bottleneck is going to be here, I'd go with remoting.

-mike
MVP

 

[Walter Zydhek]

I do need the best performance. I have created a Network "Usage"
counter using the WPcap library (via an ActiveX component called
PacketX). As this counter must handle live network traffic, and must
examine the To/From IP address of each packet, performance is a big
issue.

This by itself would not be a problem, but I need to keep the counters
in memory, and have some way of retrieving them on a regular basis by
another application (a utility
that I wrote to provide the data for MRTG).

Currently, I have it running as a service and am using remoting to allow
the client app to retrieve the counter values. I was just wondering if
I used object pooling, would it be less CPU/memory intensive.

-Walter Zydhek

 

[Michael Giagnocavo [MVP]]

But how often does the client app need to grab the data? Keeping the core
part in the same process and not crossing boundaries is going to be best.
Of course, if you're using an ActiveX component, you're already crossing COM
boundaries.

-mike
MVP

 

[Walter Zydhek]

The Client App pulls the counters every 5 minutes (for MRTG Data
gathering).

 

[Michael Giagnocavo [MVP]]

Then I would stick with remoting. I think the biggest thing you could for
performance is avoid using the COM component you're using to capture.

-mike
MVP