Re: .NET Remoting is slow!! Alternatives??

From: Ashwin Philar (ashwinphilar_at_hotmail.com)
Date: 02/20/04 

Date: 20 Feb 2004 06:50:03 -0800

Thanks for your reply.

I had tried with just a simple client that calls a remote middle tier
object that accesses the SQL Server DB with my identity and returns a
single record.

It was taking 7 seconds on a 10Mbps line and a Win2K server.

I'm going to try this again and let you know how that went.

Thanks,
Ashwin

"Sherif ElMetainy" <elmeteny.NOSPAM@wayout.net.NOSPAM> wrote in message news:<#a2MIu29DHA.1504@TK2MSFTNGP12.phx.gbl>...
> Hello
>
> As Christian mentioned, Datasets are serialized as XML even if you choose
> binary.
> So the question is whether the bottle neck is the generation and parsing of
> the xml (CPU work) or is it the network problem (Bandwidth)?
> If it is a network problem, you can fix it by using data
> compression/decompression sink, this will require more CPU work, but will
> save a lot of network traffic.
>
> You can also yes TCP instead of IIS, and you can still use windows
> authentication. Example here
> http://msdn.microsoft.com/netframework/using/understanding/networking/remoting/default.aspx?pull=/library/en-us/dndotnet/html/remsspi.asp
>
> May be you can also modify your code, such that you cach some data in the
> client, for example a list of countries is not likely to change, so getting
> this data only once and cashing it in the client can be nice. This will
> minimize round trips to the server.
>
> Also try to make you data come on one call using out parameters, if you have
> 2 methods each returing an object and are always called right after each
> other, make one methods that returns the 2 objects, thus making only one
> trip to the server.
>
>
> Best regards
> Sherif
>
> "Ashwin Philar" <ashwinphilar@hotmail.com> wrote in message
> news:33fe2089.0402190728.461f21b9@posting.google.com...
> > Hi!! Everyone,
> >
> > This is what I want to do:
> >
> > 1) Users log on to domain
> > 2) All authentication is based on domain user identity
> >
> > This is what I am doing:
> >
> > 1) I can host my remote components only in IIS because of reasons
> > stated
> > above.
> > 2) I am using HTTP with Binary formatting
> > 3) Passing DataSets to clients
> >
> > This is my problem:
> >
> > 1) .NET Remoting is slow when DataSets are passed!!
> >
> > I have tried converting DataSets to serializable object arrays, but
> > still Remoting is slow!!
> >
> > I am building an Intranet application, how can I use a distributed
> > architecture?
> >
> > Please let me know if your experience contradicts mine and also let me
> > know if you have using alternatives, if any.
> >
> > Regards,
> > Ashwin Philar

Relevant Pages

  • Re: What doesnt lend itself to OO?
    ... >> proxy and instructs the server to constuct the real object. ... rather than client code. ... If 'clock' is instantiated in the server, ... > for the server interface at the OOA level. ...
    (comp.object)
  • This is going straight to the pool room
    ... or not the client has privilege to do what they're trying to do, ... The server environment is this: ... 3GL User action Routines that Tier3 will execute on your behalf during the ... Routine Name: USER_INIT ...
    (comp.os.vms)
  • [Full-Disclosure] R: Full-Disclosure Digest, Vol 3, Issue 42
    ... Full-Disclosure Digest, Vol 3, Issue 42 ... SD Server 4.0.70 Directory Traversal Bug ... Arkeia Network Backup Client Remote Access ...
    (Full-Disclosure)
  • Re: What doesnt lend itself to OO?
    ... > rather than client code. ... no way to do that without also touching the object with clock semantics ... will not encapsulate both clock semantics and network semantics. ... The server can do whatever it wants ...
    (comp.object)
  • RE: Fax monitor incoming + outgoing calls?
    ... problem between the client computer and the SBS server. ... Client is using the internal IP address of the SBS server as the ... To the folder redirection GPO issue: ...
    (microsoft.public.windows.server.sbs)
Loading