Re: .NET Remoting slow, why?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

What protocol are you using as a transport channel?


--
Regards,
Robson Siqueira
Enterprise Architect
"Solitude" <Solitude@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:940CEB1D-38B4-49AB-8D7D-8982D4417BA0@xxxxxxxxxxxxxxxx
Also forgot to mention I was hosting it on my own remote server and me and
my
friend connected to it through our remoting speedy. Then on his server I
was
connecting to it very slowly. We are in the same area.

"Solitude" wrote:

So we aren't sending too much data back and forth.

Would implementing ISerializable on our objects and doing our own
serialization speed this up like some have suggested elsewhere?

Cause when I log into my Verizon wireless internet it takes even longer,
but
that internet is pretty fast. But someone was telling me doing
ISerializable
wouldn't matter cause if that was the problem then all connections
regardless
of the speed would be having the same slow problem. Is this true?

"Spam Catcher" wrote:

=?Utf-8?B?U29saXR1ZGU=?= <Solitude@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
news:14B5877E-384A-4A8A-8109-EA08A8DD7698@xxxxxxxxxxxxx:

Hi,

We have a tiered application and we are using remoting and the
trasportation method. This works fabulous as expected by just
connecting to local host. But when we go over to a remote server it
goes from milliseconds to 4-5 seconds to complete a simple request.

Are you serializing a lot of data?

Is there anyway to improve our remoting, we are using a
BinaryFormatProvider to send it over in binary format. And we have
compression enabled and encryption working using GenuineChannels.
Having our objects that are remoted implement ISerializable won't
improve that will it? Cause if it was serialization slowness problem
wouldn't all senarios experience this slowness? Could it be
GenuineChannels that is making this all slow?


I found if you don't serialize too much data, remoting is fast.
However, if
you're sending a lot of objects back and forth it gets quite slow
quickly.



.

Relevant Pages

  • Generic deserialization
    ... My .NET approach is to instead use a "message server service". ... CONSUMER objects. ... Here is my extreme lack of knowledge about serialization... ... Via the remoting method, I was able to send from a SOURCE to the ...
    (microsoft.public.dotnet.framework.remoting)
  • Re: Any caching in remoting?
    ... > I have a question related to any caching mechanisms in remoting. ... > service provider are located in the same IIS server. ... > serialization process if an object was already serialized? ...
    (microsoft.public.dotnet.framework.remoting)
  • Re: .NET Remoting slow, why?
    ... If I want performance is remoting not the way to go? ... connecting to it very slowly. ... Cause if it was serialization slowness problem ... GenuineChannels that is making this all slow? ...
    (microsoft.public.dotnet.framework.remoting)
  • Re: Forms authentication - change password
    ... Contact the server administrator. ... I think your authentication validation method needs to be set to ... the change password feature within ISA ... | | meant not connecting to a Global Catalog. ...
    (microsoft.public.isa)
  • Re: SBS Slow user logons problem
    ... Microsoft MVPs ... Are the workstations and Server all connecting their nics to a router? ...
    (microsoft.public.windows.server.sbs)