Re: Web Service Performance

From: Steve Drake (Steve_at__NOSPAM_.Drakey.co.uk)
Date: 01/29/05 

Date: Sat, 29 Jan 2005 19:04:36 -0000

serialization is quite fast, except runtime serialization on objects like
datasets.

When request is made, it goes through (i may be wrong with some of these
steps but you will get the picture) HTTP as a POST, IIS passes this to
ASP.NET, ASP.NET runs your CODE, your CODE returns data, the DATA is
serialized as sent to the requestor via HTTP the requestor desterilizes the
OBJECT.

if you want to test serialization on its own, you could do some tests,
also..... web service in general scale better, eg one request may seam slow
but when you start adding load its starts to perform very well compared to
other remote methods.

but..... you should not use SOAP on the same server? why would you do this?

Steve

"mterzich" <mterzich@discussions.microsoft.com> wrote in message
news:0AA869D8-6C70-463E-A31F-CFB7D55FBAB8@microsoft.com...
> If your saying the wire shouldn't be much of an issue, then the
> serialization/deserialization must be the poorest written code ever since
it
> adds between 1/4 and 1/2 second to the operation to transmit and receive
a
> 4KB to 8KB data set. To me a poorly wtitten serialization/deserialization
> operation shouldn't take more than 5 ms on a 3.0 giga hertz P4 machine. It
> still sounds like it is the wire since I'm still in testing on my Windows
> 2000 Pro which is on a cable modem with 3.0Mb/128Kb external speed. At the
> 128Kb upload speed (about 12KB), that would explain the extra 1/4 to 1/2
> second.
>
> "ranjan.listserv@gmail.com" wrote:
>
> > On Fri, 28 Jan 2005 21:59:01 -0800, mterzich wrote:
> >
> > > Since I am using localhost in the url, I would think that the
performance
> > > shouldn't be greatly affected by line speed or is the transfer speed
limited
> > > by the line speed even though it is internal? Any ideas why there
would be
> > > such a great difference in performance between the direct API call and
the
> > > http call?
> >
> > Serialization + wire(normally not noticable for a localhost address) +
> > Deserialization
> > --
> >
> >
> > http://dotnetjunkies.com/weblog/dotnut
> >

Relevant Pages

  • Re: Web Service Performance
    ... Also don't measure the first time as you don't want to include assembly load ... >> serialization is quite fast, ... >> When request is made, it goes through (i may be wrong with some of these ... >>> still sounds like it is the wire since I'm still in testing on my ...
    (microsoft.public.dotnet.framework)
  • [PATCH 5/6] ide: use lock bitops for ports serialization
    ... Subject: ide: use lock bitops for ports serialization ... together with lock bitops to provide new ports serialization method. ... * A hwgroup is a serialized group of IDE interfaces. ... * and then initiates processing of the top request from the request queue. ...
    (Linux-Kernel)
  • Re: Web Service Performance
    ... > serialization is quite fast, except runtime serialization on objects like ... > When request is made, it goes through (i may be wrong with some of these ... > if you want to test serialization on its own, you could do some tests, ... >> still sounds like it is the wire since I'm still in testing on my ...
    (microsoft.public.dotnet.framework)
  • [PATCH] ide: use lock bitops for ports serialization (v2)
    ... Subject: [PATCH] ide: use lock bitops for ports serialization ... * A hwgroup is a serialized group of IDE interfaces. ... * and then initiates processing of the top request from the request queue. ...
    (Linux-Kernel)
  • Re: Reducing the size of a serialized object.
    ... Serialization I find that the best place to look is the JavaDoc's ... Because a lot of beans are being sent over the wire to the RMI server ... > every day I want to try to keep down the size of the serialized bean. ...
    (comp.lang.java.programmer)
Loading