From owner-freebsd-stable@freebsd.org Mon Jun 18 12:01:49 2018 Return-Path: Delivered-To: freebsd-stable@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 D24981001D55 for ; Mon, 18 Jun 2018 12:01:48 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 76D977B399 for ; Mon, 18 Jun 2018 12:01:48 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id F190121EB9 for ; Mon, 18 Jun 2018 08:01:41 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Mon, 18 Jun 2018 08:01:41 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=FCswhxQBVk2etLJOALpduT3gZLkkr QB/NvLJsGz/Ups=; b=bnQWPIxdcM4UPPft/ofgaE9MyeyGXxf5wo4EPjoi6aCiI jDoaGT9jzUtkYT6TnX9EVcU1G5CdUSRVQLyFd39eyStTh84YqFeonl3dW9/LFb+B nu6ReQQ6kVQs3JteiGAma42oWkRkg52fvSMgG818VLWbpYqi+k/jZ412qBG/JtvH sFV8IRlx02xa3pVHhf7fmUeCl0ZJE/Q+pqvtciVtwewpP9BJgc8WRbfyauqh0qCa SpqbofH/g2gLMgb0tjudU7B9QIptxkLFBOjpXBjWn4nMhLdXVxIpWMAdxUxxKQD2 6htGUd8EBEmPm1+VmCl8bhD3gXrV7/2lv/WOeC35g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=FCswhx QBVk2etLJOALpduT3gZLkkrQB/NvLJsGz/Ups=; b=FqRTEk7H/lihhHDuj3wdJf 13uCrJecppp+olsGCZAsK/8Ik7RtGXKVCqY6RyX8dYqZksx/suYukDVBLZGaQ6LR V7m0LLICMmh+vAzlNH78dc/iazNeci0XR3DYI9lyUuYijlu3sT+r3rACokFyE3Q6 x9b57XhdmBsXNwgA2WnYYIl1aOkrvh5hxmB9Kwqv3HVa6NH57MDZBL/7xxhL38EJ yGRry1wKU8B9qFEWU9s8LLD4IxthKswe8USferp64QUuJwDSAcOjg4ioni/Lm0G8 +DKN0FcMmQ/89CSPvI1q5Tmp82llxqXuP5amzjtSezzsbtuQkM06ZHBM3wtMNibg == X-ME-Proxy: X-ME-Sender: Received: from desktop.local (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id 80C87E4AB7 for ; Mon, 18 Jun 2018 08:01:41 -0400 (EDT) Subject: Re: lightly loaded system eats swap space References: To: freebsd-stable@freebsd.org From: tech-lists Organization: none Message-ID: <7817cd74-ba4e-100d-72a2-050d387f90b4@zyxst.net> Date: Mon, 18 Jun 2018 13:01:40 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jun 2018 12:01:49 -0000 On 18/06/2018 00:04, Adam wrote: > Based upon the output neither ram nor swap seems like similar spec so I > wonder if you could say what you mean by that. server with the problem: last pid: 62387; load averages: 0.07, 0.10, 0.08 up 30+01:30:01 12:46:40 48 processes: 1 running, 47 sleeping CPU: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle Mem: 5404K Active, 1218M Inact, 4927M Laundry, 117G Wired, 1392M Buf, 2116M Free ARC: 109G Total, 2982M MFU, 105G MRU, 288K Anon, 385M Header, 638M Other 104G Compressed, 105G Uncompressed, 1.01:1 Ratio Swap: 4096M Total, 3383M Used, 713M Free, 82% Inuse This server runs 1 bhyve instance using 16GB. It has 128GB RAM. server without a problem: last pid: 84491; load averages: 0.03, 0.02, 0.02 up 17+14:39:31 12:47:33 27 processes: 1 running, 26 sleeping CPU: % user, % nice, % system, % interrupt, % idle Mem: 2915M Active, 25G Inact, 9947M Laundry, 28G Wired, 1572M Buf, 59G Free ARC: 22G Total, 3379M MFU, 19G MRU, 781K Anon, 64M Header, 974K Other 22G Compressed, 29G Uncompressed, 1.33:1 Ratio, 121M Overhead Swap: 35G Total, 3747M Used, 32G Free, 10% Inuse This server runs 10 bhyve instances of various RAM sizes, from 4GB to 32GB. It also has 128GB RAM installed. This is what I mean by "similar spec", I mean in terms of RAM. This server doesn't usually show swap as being in use, but I can actually account for this, as there is memory overcommitment here. My point is that 'server with problem' should not show a resources issue with just one bhyve instance using 16GB RAM but apparently it is, and I don't know why. I am starting the VMs by hand, without any third-party application, and I'm not wiring memory on the command line. thanks, -- J.