Re: .NET Remoting is slow!! Alternatives??
From: Sherif ElMetainy (elmeteny.NOSPAM_at_wayout.net.NOSPAM)
Date: 02/20/04
- Next message: Alex Brunner, ALL CONSULTING AG, Switzerland: "Re: How to fix Big Red Cross on the screen"
- Previous message: Welman Jordan: "Re: Virtual Memory Leak? What's goin' on?"
- In reply to: Ashwin Philar: ".NET Remoting is slow!! Alternatives??"
- Next in thread: Ashwin Philar: "Re: .NET Remoting is slow!! Alternatives??"
- Reply: Ashwin Philar: "Re: .NET Remoting is slow!! Alternatives??"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 20 Feb 2004 06:39:24 +0200
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
- Next message: Alex Brunner, ALL CONSULTING AG, Switzerland: "Re: How to fix Big Red Cross on the screen"
- Previous message: Welman Jordan: "Re: Virtual Memory Leak? What's goin' on?"
- In reply to: Ashwin Philar: ".NET Remoting is slow!! Alternatives??"
- Next in thread: Ashwin Philar: "Re: .NET Remoting is slow!! Alternatives??"
- Reply: Ashwin Philar: "Re: .NET Remoting is slow!! Alternatives??"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
