[lnkForumImage]
TotalShareware - Download Free Software
Confronta i prezzi di migliaia di prodotti.
Asp Forum
 Home | Login | Register | Search 


 

Forums >

microsoft.public.dotnet.framework.remoting

Performance of the "Remoting"

Hawix

9/20/2004 2:08:00 PM

Hi All,

I need make an application server designed for 200 online clients. The
Remoting technology is very nice but I'm afraid that is not efficient for
hunders online clients.
I want to make application server which is designed for mediating between
client and SQL database server. More of the processes will be executed in
SQL database, so my application server calls stored procedures only (for
reading and updating data).

Does anybody know what's the performace of Remoting technology?

Contexts:
1) What the hardware use for the server (processor(s), RAM)?
2) Does Remoting is stable (for example: when one or more of the active
thread is hang)?
3) What the server platform use: Win2000 Server, Win2003 Server or may be
WinXP is enough?
4) Does the TCP channel is more efficient then HTTP (for "point to point"
connection of course)?
5) Does the DataSet component is enough for exchange data beetwen client and
application server side?

Best Regards,
Marcin Lis
4 Answers

Ken Kolda

9/20/2004 5:38:00 PM

0

Here are some articles that may help answer some of your performance-related
questions. I've also included some comments inline below.

http://msdn.microsoft.com/library/en-us/dnbda/html/bdadotnet...
http://msdn.microsoft.com/library/en-us/dnpag/html/scalenetc...

Ken


"Hawix" <hawix@wytnijto_op.pl> wrote in message
news:cimo7q$7so$1@news.onet.pl...
> Hi All,
>
> I need make an application server designed for 200 online clients. The
> Remoting technology is very nice but I'm afraid that is not efficient for
> hunders online clients.
> I want to make application server which is designed for mediating between
> client and SQL database server. More of the processes will be executed in
> SQL database, so my application server calls stored procedures only (for
> reading and updating data).
>
> Does anybody know what's the performace of Remoting technology?
>
> Contexts:
> 1) What the hardware use for the server (processor(s), RAM)?

This is completely dependent on your application, what your remotign server
does, what other things the computer is doing, the number of users you need
to support, etc. I don't think there can be a simple answer for this.

> 2) Does Remoting is stable (for example: when one or more of the active
> thread is hang)?

We use remoting heavily and have been very pleased with its stability.

> 3) What the server platform use: Win2000 Server, Win2003 Server or may be
> WinXP is enough?

Take your pick -- it works on all three. If you're going to run your
remoting component under IIS, then I'd go with Win 2K3. Keep in mind that XP
Home and Pro and not considered "server" platforms, so if you plan on a
large number of users, I'd stick with 2K Server or 2003.

> 4) Does the TCP channel is more efficient then HTTP (for "point to point"
> connection of course)?

Yes, the TcpChannel will generally perform better than Http. Similarly,
using the binary formatter will be faster than using SOAP. Check out the
articles I referenced for direct comparisons of the channels/formatters.

> 5) Does the DataSet component is enough for exchange data beetwen client
and
> application server side?

Yes, DataSet can certainly be used. However, when serialized across a
remoting boundary, it must be turned into XML and then deserialized from XML
(even if using the binary formatter). This is generally inefficient, both in
performance and in bandwidth. Depending on your data structures and your
desire to get every ounce of performance out of your server, you may opt to
create your own data objects which provide a more compact representation of
your data.

>
> Best Regards,
> Marcin Lis
>
>

Robert Jordan

9/20/2004 8:11:00 PM

0

Hi Ken,

> Yes, DataSet can certainly be used. However, when serialized across a
> remoting boundary, it must be turned into XML and then deserialized from XML
> (even if using the binary formatter). This is generally inefficient, both in
> performance and in bandwidth. Depending on your data structures and your
> desire to get every ounce of performance out of your server, you may opt to
> create your own data objects which provide a more compact representation of
> your data.

There are some workarounds for this problem:

http://objectsharp.com/Blogs/datasetfaq/archive/2004/06/1...

bye
Rob

Ken Kolda

9/20/2004 9:59:00 PM

0

Robert -- thanks for that info. I hadn't seen these options before.

Ken


"Robert Jordan" <robertj@gmx.net> wrote in message
news:cindfv$1hn$03$1@news.t-online.com...
> Hi Ken,
>
> > Yes, DataSet can certainly be used. However, when serialized across a
> > remoting boundary, it must be turned into XML and then deserialized from
XML
> > (even if using the binary formatter). This is generally inefficient,
both in
> > performance and in bandwidth. Depending on your data structures and your
> > desire to get every ounce of performance out of your server, you may opt
to
> > create your own data objects which provide a more compact representation
of
> > your data.
>
> There are some workarounds for this problem:
>
> http://objectsharp.com/Blogs/datasetfaq/archive/2004/06/1...
>
> bye
> Rob

John

10/10/2004 1:06:00 AM

0

Hello:

As far as I know Remoting is not as hardware intensive as you might think.
Moreover, 200 clients is not a big number and hence I would not worry so
much about performance issues.

VKD

"Hawix" <hawix@wytnijto_op.pl> wrote in message
news:cimo7q$7so$1@news.onet.pl...
> Hi All,
>
> I need make an application server designed for 200 online clients. The
> Remoting technology is very nice but I'm afraid that is not efficient for
> hunders online clients.
> I want to make application server which is designed for mediating between
> client and SQL database server. More of the processes will be executed in
> SQL database, so my application server calls stored procedures only (for
> reading and updating data).
>
> Does anybody know what's the performace of Remoting technology?
>
> Contexts:
> 1) What the hardware use for the server (processor(s), RAM)?
> 2) Does Remoting is stable (for example: when one or more of the active
> thread is hang)?
> 3) What the server platform use: Win2000 Server, Win2003 Server or may be
> WinXP is enough?
> 4) Does the TCP channel is more efficient then HTTP (for "point to point"
> connection of course)?
> 5) Does the DataSet component is enough for exchange data beetwen client
and
> application server side?
>
> Best Regards,
> Marcin Lis
>
>