From owner-freebsd-current@freebsd.org Fri Jul 29 19:41:19 2016 Return-Path: Delivered-To: freebsd-current@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 7DD89BA81AE for ; Fri, 29 Jul 2016 19:41:19 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: from mail-qt0-x22b.google.com (mail-qt0-x22b.google.com [IPv6:2607:f8b0:400d:c0d::22b]) (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 3B3091CA0; Fri, 29 Jul 2016 19:41:19 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: by mail-qt0-x22b.google.com with SMTP id u25so72347126qtb.1; Fri, 29 Jul 2016 12:41:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=tHwOENiOgUyDWzfKSD6XbrmaWMzAsiYVH48A2tKDQUE=; b=yiMZ8ss1hPsbjrdt1HpJgiSXl5NRcRW9VUZfa9n7+BjCNUcLTXilSk2oPhFnCsUje+ NQ8Vyd1HgNaQkMc1y7fFVHBQh2JrfU+5g5Ha97PUj4Kr0mGMyj3QpKa+yBr1vxknnig/ raFtfKi9oYkEbnKQy5UnWjtfQQt2sZ8/KYz152ZCeJAh+eo3P3umh1ToJgFobrGHh6Le jfO18XHkltZwto8GBbLdCJ8gE75GYI2rhlU3tXewwGG8Uf5uVHOc2++C/E48TWZ+IUWd PXMgNj3qt4YQQebrws60s/i0VvD49FLtpVwKySM3/iTIRvdIgF13OIORMqqZ6EDDMHOz MfFA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=tHwOENiOgUyDWzfKSD6XbrmaWMzAsiYVH48A2tKDQUE=; b=b/TwdP4BddxX1bzeY74hPC0BFjvjhQV1BHERG4rH5pbtoURx7jVDsYhXDHNFgERhhQ J307gFS1w6rY55l/oVhTNAL2VS56z/fI01SMw5pgLUbF3CC2J2Uq3aq3WYOIW02TggMH Xb6IjkhJxl21tbENcHNQ7aWTImVk7ezCYxR6lm1kzv6MfTzmghOYYP5F3390rEWGm4ht Z5Fr/i4qWHinuPE5sD3i8TIg6EXdxOw0EbmP/QadcBqXiJJK0KIccZkXmYnEinlzZDti dsylNCTEHdJjnR+cJAvR5M3qBkTOCQMHF8uETYJrNO/zFjiMCkyRQnvuRCG7EdXDbj8t +JbQ== X-Gm-Message-State: AEkoousT2ogHwfHhvCOkX4BccgqFhJqZMp5bxCXGsjjD8bitm80hojQlATj2iye/z/PkeJHyID0lJiqqVu8pdw== X-Received: by 10.200.49.129 with SMTP id h1mr68779368qte.103.1469821278152; Fri, 29 Jul 2016 12:41:18 -0700 (PDT) MIME-Version: 1.0 Received: by 10.233.216.194 with HTTP; Fri, 29 Jul 2016 12:41:17 -0700 (PDT) In-Reply-To: <18fe457f-c99e-8747-8692-e199f356f6d5@freebsd.org> References: <20160729200458.2bb2c6ca.ohartman@zedat.fu-berlin.de> <18fe457f-c99e-8747-8692-e199f356f6d5@freebsd.org> From: Ngie Cooper Date: Fri, 29 Jul 2016 12:41:17 -0700 Message-ID: Subject: Re: CURRENT: memory leak? To: Allan Jude Cc: FreeBSD Current Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jul 2016 19:41:19 -0000 On Fri, Jul 29, 2016 at 12:03 PM, Allan Jude wrote: > On 2016-07-29 14:04, O. Hartmann wrote: >> >> I realise an exorbitant memory usage of FreeBSD CURRENT ( FreeBSD >> 12.0-CURRENT #16 >> r303470: Fri Jul 29 05:58:42 CEST 2016 ). Swap space gets eaten up while >> building >> world/kernel and/or ports very quickly. >> >> I see this phenomenon on different CURRENT systems with different RAM (but >> all ZFS!). No >> box is less than 8 GB RAM: one 8GB, another 16, two 32 GB. An older XEON >> Core2Duo server >> with postgresql 9.5/postgis acting on some OSM data etas up all of its 32 >> GB and >> additional 48GB swap - never seen before with 11-CURRENT. >> >> I didn't investigate the problem so far since I realized this memory >> hunger of 12-CURRENT >> just today on several boxes compiling world, eating up all the memory, >> staring swapping >> and never relax even after hours from the swapped memory. >> >> Is this a known phenomenon or am I seeing something mystique? >> >> Regards, >> >> Oliver >> > > Do you have the output of 'top', the first few lines > > Specifically, is there very high 'Other' usage, on the ZFS ARC line? `vmstat -Hm | sort -rnk 2,3 | head -n 10` might be helpful if the memory used is in kernel space. Thanks, -Ngie