SLOW .NET client for custom HTTP server


DevX Home    Today's Headlines   Articles Archive   Tip Bank   Forums   

Results 1 to 5 of 5

Thread: SLOW .NET client for custom HTTP server

  1. #1
    ali Guest

    SLOW .NET client for custom HTTP server


    Hi,

    I am using my own HTTP/SOAP server to handle requests. If calling it from
    tomcat axis leads to 300 msg/s, calling it from a .NET (C++ Managed) client
    leads to 2 msg/s with a CPU 99% idle !

    This same .NET client works fine (250 msg/s) with a .NET server. Has anybody
    encountered the same pb ?

    Are .NET clients requiring a certain type of advanced HTTP exchange to perform
    a good job ? Are they "Sleep(500)" instructions in the .NET client code just
    to be sure that only .NET server are used ???

    Best Regards,
    ALi


  2. #2
    Guest

    Re: SLOW .NET client for custom HTTP server


    "ali" <vc.@127.0.0.1> wrote:
    It appears that the .NET client closes the connexion and reopens it after
    each call.

    How do I control this ?

    >
    >Hi,
    >
    >I am using my own HTTP/SOAP server to handle requests. If calling it from
    >a custom HTTP/SOAP client leads to 300 msg/s, calling it from a .NET (C++

    Managed) client
    >leads to 2 msg/s with a CPU 99% idle !
    >
    >This same .NET client works fine (250 msg/s) with a .NET server. Has anybody
    >encountered the same pb ?
    >
    >Are .NET clients requiring a certain type of advanced HTTP exchange to perform
    >a good job ? Are they "Sleep(500)" instructions in the .NET client code

    just
    >to be sure that only .NET server are used ???
    >
    >Best Regards,
    >ALi
    >



  3. #3
    ali Guest

    Re: SLOW .NET client for custom HTTP server


    For info, it is slow because you HAVE to respond HTTP 1.1/Continue after receiving
    the header.

    <vb.@127.0.0.1> wrote:
    >
    >"ali" <vc.@127.0.0.1> wrote:
    >It appears that the .NET client closes the connexion and reopens it after
    >each call.
    >
    >How do I control this ?
    >
    >>
    >>Hi,
    >>
    >>I am using my own HTTP/SOAP server to handle requests. If calling it from
    >>a custom HTTP/SOAP client leads to 300 msg/s, calling it from a .NET (C++

    >Managed) client
    >>leads to 2 msg/s with a CPU 99% idle !
    >>
    >>This same .NET client works fine (250 msg/s) with a .NET server. Has anybody
    >>encountered the same pb ?
    >>
    >>Are .NET clients requiring a certain type of advanced HTTP exchange to

    perform
    >>a good job ? Are they "Sleep(500)" instructions in the .NET client code

    >just
    >>to be sure that only .NET server are used ???
    >>
    >>Best Regards,
    >>ALi
    >>

    >



  4. #4
    Bobby Guest

    Re: SLOW .NET client for custom HTTP server


    What is actually causing the client not to scale? Is there a solution?

    "ali" <none@none.com> wrote:
    >
    >For info, it is slow because you HAVE to respond HTTP 1.1/Continue after

    receiving
    >the header.
    >
    ><vb.@127.0.0.1> wrote:
    >>
    >>"ali" <vc.@127.0.0.1> wrote:
    >>It appears that the .NET client closes the connexion and reopens it after
    >>each call.
    >>
    >>How do I control this ?
    >>
    >>>
    >>>Hi,
    >>>
    >>>I am using my own HTTP/SOAP server to handle requests. If calling it from
    >>>a custom HTTP/SOAP client leads to 300 msg/s, calling it from a .NET (C++

    >>Managed) client
    >>>leads to 2 msg/s with a CPU 99% idle !
    >>>
    >>>This same .NET client works fine (250 msg/s) with a .NET server. Has anybody
    >>>encountered the same pb ?
    >>>
    >>>Are .NET clients requiring a certain type of advanced HTTP exchange to

    >perform
    >>>a good job ? Are they "Sleep(500)" instructions in the .NET client code

    >>just
    >>>to be sure that only .NET server are used ???
    >>>
    >>>Best Regards,
    >>>ALi
    >>>

    >>

    >



  5. #5
    bobby Guest

    Re: SLOW .NET client for custom HTTP server


    Apparently MS .NET only allows a maximum of 2 HTTP connections on a client
    by default. If you edit this setting you should get a much higher throughput.
    Another thing to try is to disable the use of Nagle's algorithm on the client.

    "Bobby" <none@none.com> wrote:
    >
    >What is actually causing the client not to scale? Is there a solution?
    >
    >"ali" <none@none.com> wrote:
    >>
    >>For info, it is slow because you HAVE to respond HTTP 1.1/Continue after

    >receiving
    >>the header.
    >>
    >><vb.@127.0.0.1> wrote:
    >>>
    >>>"ali" <vc.@127.0.0.1> wrote:
    >>>It appears that the .NET client closes the connexion and reopens it after
    >>>each call.
    >>>
    >>>How do I control this ?
    >>>
    >>>>
    >>>>Hi,
    >>>>
    >>>>I am using my own HTTP/SOAP server to handle requests. If calling it

    from
    >>>>a custom HTTP/SOAP client leads to 300 msg/s, calling it from a .NET

    (C++
    >>>Managed) client
    >>>>leads to 2 msg/s with a CPU 99% idle !
    >>>>
    >>>>This same .NET client works fine (250 msg/s) with a .NET server. Has

    anybody
    >>>>encountered the same pb ?
    >>>>
    >>>>Are .NET clients requiring a certain type of advanced HTTP exchange to

    >>perform
    >>>>a good job ? Are they "Sleep(500)" instructions in the .NET client code
    >>>just
    >>>>to be sure that only .NET server are used ???
    >>>>
    >>>>Best Regards,
    >>>>ALi
    >>>>
    >>>

    >>

    >



Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
HTML5 Development Center
 
 
FAQ
Latest Articles
Java
.NET
XML
Database
Enterprise
Questions? Contact us.
C++
Web Development
Wireless
Latest Tips
Open Source


   Development Centers

   -- Android Development Center
   -- Cloud Development Project Center
   -- HTML5 Development Center
   -- Windows Mobile Development Center