Actually, if your application uses UDP then it is most likely designed to tolerate some packet loss. That is the whole point of UDP. With TCP you get handshakes, checksums, acknowledgements, but you pay for it with some overhead and sacrificing some speed. With UDP you get none of that, instead you get a fast protocol with low overhead. At the same time your client program sends it's packets and doesn't care if they get there or not.

Perhaps you need to rethink your strategy regarding this UDP application. Dropping some packets may not be so bad in the long run. Or what about rewriting the socket code in C so it can suck down the packets faster?

Hope this gives you some ideas.

Cheers

In reply to Re: How to increase Socket buffer size? by pzbagel
in thread How to increase Socket buffer size? by sureshr

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.