From owner-freebsd-net@freebsd.org Fri May 25 11:27:27 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0FF9FF7973E for ; Fri, 25 May 2018 11:27:27 +0000 (UTC) (envelope-from raimund.sacherer@logitravelgroup.com) Received: from mail-it0-x230.google.com (mail-it0-x230.google.com [IPv6:2607:f8b0:4001:c0b::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 83D257D6C9 for ; Fri, 25 May 2018 11:27:26 +0000 (UTC) (envelope-from raimund.sacherer@logitravelgroup.com) Received: by mail-it0-x230.google.com with SMTP id 144-v6so6331744iti.5 for ; Fri, 25 May 2018 04:27:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=logitravelgroup-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:reply-to:from:date:message-id :subject:to; bh=qd4pPk5zjFh7V6ABCCP76wDA3sC0FrxPnlhhXC9z6qs=; b=IJE0U0G0ppuuBcx61xFUTlbEBCZ46O/hHzjN/j6aibRzEMhcNGWhl6etjLt4XFpOn7 eDfFiWSL9cNm41EzNZuA7DtRBRmRWOE95Fsf+NwyCmtrzHFT7IIJrb7tvAMkJoc8Hw8t vyca89QPCOPANwArC0PNSMkftfQBqHPIo7MCMKLEXSQ5Xy8qaVegZeYlA9uXcB2N/VBb mUR+U5nCk2XjXd/0y4zGl1Qvln6H0iYJz98yuJKAXf+FnZK2UYv+3ZgwgnSUYDuJRnM7 jL7Zl/4Xs7xSzxldLSVK/uLyB+6/zxJJogwvfqtF3oKQVcJpGSz6NWXDIQFnQqmhqBnE 8/Ug== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:reply-to :from:date:message-id:subject:to; bh=qd4pPk5zjFh7V6ABCCP76wDA3sC0FrxPnlhhXC9z6qs=; b=Lh+fIjlK4yArR+6GtPR/iu/KM+BCTryvW+ErCearKudx/dB19Ti0qSrcyqU0K5YWPh 50VExBZUpi/Et5V/JCM5MAUHAolVBcCnRoC+W/olTSYbExZXqQFQ+URlZGRAqDu0JSm8 7jxqPMdyp4aTLItSODOXXQqcUkJ/Kja/kNvq2y8ijkTabCpGpZe1bX5qZGNWtMDUgJl6 6D3vui2iY1T33Njxf9D1Y37erZo2R+KtxNzJLZVeIu9JM19JHJEdOAcaUxsOvcP0rgVl 9MWAe0WwGu9VuAtKSP/VXE+3piOJxcyWIaIzVoYYunGi/yHBLSBhyWWjXoBxrmoVO6ec bmpQ== X-Gm-Message-State: ALKqPwfDf4zlo6E3V/DPYjuBrzEQtRv40WGehD1R/GPxjumzsAkxqOR9 8N4FzHIdlAQoOl+td7BjCBW1SQ05l70RoBi21SLud5Ve X-Google-Smtp-Source: AB8JxZojvjRSBBMCrnMqdnDnfyMr3GoFdLK+5x8Go+j5FkHH2MGVB7vXyYP+E651z/vNzOouRXCnbOajnZkjCCuEzAE= X-Received: by 2002:a24:438f:: with SMTP id s137-v6mr1512543itb.28.1527247645826; Fri, 25 May 2018 04:27:25 -0700 (PDT) MIME-Version: 1.0 References: <5B07012D.4050003@grosbein.net> In-Reply-To: Reply-To: rs@logitravel.com From: Raimund Sacherer Date: Fri, 25 May 2018 13:28:00 +0200 Message-ID: Subject: Fwd: systat -ip, socket buffer full To: freebsd-net@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 May 2018 11:27:27 -0000 On Thu, May 24, 2018 at 8:16 PM Eugene Grosbein wrote: > 24.05.2018 21:09, Ray wrote: > > > when checking systat -ip I see the value for "socket buffer full" with > > values different from 0, I see 1, 2, up to 55 in one occasion. > > > > I asked on IRC and it was mentioned I should try to up > > kern.ipc.soacceptqueue to 1024 from the default 128, but I could still > see > > values over 0 in "socket buffer full". > > > > How can I tune this buffer? > > > > We have a lot of UDP traffic (the server is a PBX serving around 200 > agents > > with avg 50 concurrent calls. > > Each (udp) socket has its own limit on receiving buffer size and it is > application's duty > to set its size to right value using setsockopt() function. > You should read your PBX manual on how to configure it to use larger > buffers. > I will check this out. > > As last resort, you can raise sysctl kern.ipc.maxsockbuf that establishes > default value > for size of such buffers that is used when application does not change > defaults. > However, it may affect many applications in the system and lead to > overflow of kernel memory pools > unless you know what are you doing, has plenty of free physical memory and > raised kernel limits > accordingly, so better start with PBX documentation. > Thank you, I might try that, i checked and the value on my system is 2097152. How can I check if I hit this buffer wall? Is there a monitoring tool which can tell me more stats about this buffer use? Thank you, best Ray