Mike Tancsa writes: > > > net.inet.ip.intr_queue_maxlen from 50 to 100. and there didnt seem to be > > > any positive results in terms of lessening the rate of > > > net.inet.ip.intr_queue_drops. > > > >This is consistent with the situation where packets are received > >at a rate faster than they are being consumed. No matter how big > >your queue is, it's going to fill up eventually and overflow, and > >all you're doing by increasing the queue length is adding latency > >to all of those packets that you do process. > > Hi, thanks for the info. But wont I still pay a price, presumably at the > application layer for any packets that are lost and retransmitted ? Apart > from pinging the other side of the OC-3 or ethernet connection and > measuring the response time, how can I see how much latency is added by > increasing these buffers ?
If the forwarding path is maxed out, then it is the application layer's responsibility to back off (think TCP). Pinging is an excellent way to determine latency. -Archie __________________________________________________________________________ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
