From owner-freebsd-virtualization@freebsd.org Fri Dec 1 09:39:27 2017 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 40BBDDF8EFA for ; Fri, 1 Dec 2017 09:39:27 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from forward101o.mail.yandex.net (forward101o.mail.yandex.net [IPv6:2a02:6b8:0:1a2d::601]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EB33E78573 for ; Fri, 1 Dec 2017 09:39:26 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from mxback10j.mail.yandex.net (mxback10j.mail.yandex.net [IPv6:2a02:6b8:0:1619::113]) by forward101o.mail.yandex.net (Yandex) with ESMTP id 214761345A8F for ; Fri, 1 Dec 2017 12:39:23 +0300 (MSK) Received: from smtp3o.mail.yandex.net (smtp3o.mail.yandex.net [2a02:6b8:0:1a2d::27]) by mxback10j.mail.yandex.net (nwsmtp/Yandex) with ESMTP id 28lZuTZf9z-dNgKCrj0; Fri, 01 Dec 2017 12:39:23 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=passap.ru; s=mail; t=1512121163; bh=BOwZkwJCM35St2QaVYIChhbGzouiKkz1g64RPmT6Aa8=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=WT68vBm09lXcaWiPGkthlHqDYLGdxIh0xKdA+KIm7uuUrTz6EyJUMhkPYeUZPp7cP jOViV/SU1mBVMD2+Jb22zz0K/1sLQKYApTKgCzrDoWrUHdGxsu/M9zF37wyTdrOORg sXyaOzsbd8AGxhqUwItJ7s0/Fp04MXiXTQ0PY0JQ= Received: by smtp3o.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id jkX3X6C5Un-dMS0f9Gm; Fri, 01 Dec 2017 12:39:22 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=passap.ru; s=mail; t=1512121162; bh=BOwZkwJCM35St2QaVYIChhbGzouiKkz1g64RPmT6Aa8=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=jVz3etsB19u5tlVRhC/HyKWPIQF6yNJdINuw/HSOIV1rYtUVWHtjFYvJVyhi21P9p Chpo9cQqb9duVTZ6kZtdXs5k1BDzf5e5k/vt0v5XMXgS86av75vJyb59Ykg7BksO1L 8f4MNw9tcow4WgD2vJh28ST4/kO8OXyoizfpeVXw= Authentication-Results: smtp3o.mail.yandex.net; dkim=pass header.i=@passap.ru Subject: Re: bhyve uses all available memory during IO-intensive operations To: freebsd-virtualization@freebsd.org References: From: Boris Samorodov Message-ID: Date: Fri, 1 Dec 2017 12:39:22 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Dec 2017 09:39:27 -0000 Hi Dustin, All, 01.12.2017 02:15, Dustin Wenz пишет: > bhyve will quickly grow to use all available system memory I'd say that some logs/stats/values should help here. JFYI: I've just got a success importing of an earth base OSM/nominatim/postgis at bhyve guest (CentOS-7.3, 14 CPU, 36GB RAM, 1TB HDD). The process lasted for about 14 days. It was really IO and CPU intensive. No other bhyve guests and the host as well have been disturbed. The host OS is FreeBSD-HEAD though. -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve