Date: Wed, 17 Feb 2016 13:15:13 -0600 From: dweimer <dweimer@dweimer.net> To: =?UTF-8?Q?Efra=C3=ADn_D=C3=A9ctor?= <efraindector@motumweb.com> Cc: stable@freebsd.org, owner-freebsd-stable@freebsd.org Subject: Re: intr using Swap Message-ID: <d6b6f3959b51a4ba3b8ab86de5931ae2@dweimer.net> In-Reply-To: <56C4C244.8070805@motumweb.com> References: <56C4AF81.3040202@motumweb.com> <87f6fb602e0ad11b7600c70a08d74c30@dweimer.net> <56C4C244.8070805@motumweb.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2016-02-17 12:56 pm, Efraín Déctor wrote: > El 17/02/2016 a las 12:34 p. m., dweimer escribió: > >> I believe you are incorrectly reading it, the first character of the state line being a W Marks an idle interrupt thread, W only means swapped out if its an additional character in the section. >> >> man ps >> [...snip...] >> state The state is given by a sequence of characters, for example, >> ``RWNA''. The first character indicates the run state of the >> process: >> [...snip...] >> W Marks an idle interrupt thread. >> [...snip...] >> Additional characters after these, if any, indicate additional >> state information: >> [...snip...] >> W The process is swapped out. >> [...snip...] >> >> Even when there is available memory if an item has already been swapped it wont return to physical memory until the process needs access that memory. Its not uncommon to see systems that had a brief memory constraint leave some swap long after the memory has been cleared up. > > Hello. > > Thank you for your response. > > Using only _ps ax_ doesn't show any process being in swap. How can I determine what processes are being swapped out? They may not show as swapped unless the entire process is actually swapped, which would be unlikely to occur. Personally I wouldn't worry about it, the only thing I can think of is to restart processes one at a time to see which one clears up the swap usage. Granted you may see a little clear after each process. The more important task would be to determine what caused the memory to run out in the first place, and decide if its going to be a frequent enough occurrence to justify adding physical memory to the system. There is likely some way to find out what is using it, but that is beyond my knowledge. -- Thanks, Dean E. Weimer http://www.dweimer.net/ From owner-freebsd-stable@freebsd.org Wed Feb 17 22:44:59 2016 Return-Path: <owner-freebsd-stable@freebsd.org> Delivered-To: freebsd-stable@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 5453AAAA4A6 for <freebsd-stable@mailman.ysv.freebsd.org>; Wed, 17 Feb 2016 22:44:59 +0000 (UTC) (envelope-from efraindector@motumweb.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 32CD11E6B for <freebsd-stable@freebsd.org>; Wed, 17 Feb 2016 22:44:59 +0000 (UTC) (envelope-from efraindector@motumweb.com) Received: by mailman.ysv.freebsd.org (Postfix) id 2FC29AAA4A3; Wed, 17 Feb 2016 22:44:59 +0000 (UTC) Delivered-To: stable@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 2E7F0AAA4A2 for <stable@mailman.ysv.freebsd.org>; Wed, 17 Feb 2016 22:44:59 +0000 (UTC) (envelope-from efraindector@motumweb.com) Received: from mail-ob0-x231.google.com (mail-ob0-x231.google.com [IPv6:2607:f8b0:4003:c01::231]) (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 EF78A1E69 for <stable@freebsd.org>; Wed, 17 Feb 2016 22:44:58 +0000 (UTC) (envelope-from efraindector@motumweb.com) Received: by mail-ob0-x231.google.com with SMTP id wb13so38903231obb.1 for <stable@freebsd.org>; Wed, 17 Feb 2016 14:44:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=motumweb-com.20150623.gappssmtp.com; s=20150623; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-type; bh=PwlOY/3Wb2EdFfqSMwSi41NXutBtBCRMCt9m8RemI5g=; b=sUD0T2LWf9BzVqGYdiBHrxqwGIj5RRoEK9yQSi0d4Yt9cj66EprZ5LB5bOSDeaWdjk q23afLcbrm4qh5EgN1d05PstkAPuSZpnDwu5UayQwc7WROgc2KZYW1U01G3yysE0B1lE uJ4LjpbsSou29mx46K4DHCv49izS0P/AGhZA3tmigvS+W2cJ+MDCDzfHeDnLjhIFVTxK zxucxLCt5kMxMdmydogztpf4yHW7u5a2RkzOG0ToNBxsWPH77Ox6iVdHobLv6L1MpSVM 9ojDDTk5bIqy4e3vhLpEqX8N977yHEntZixav7j/HkvFtki6kdeG/fi56QBBFb/5j6e1 8psg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-type; bh=PwlOY/3Wb2EdFfqSMwSi41NXutBtBCRMCt9m8RemI5g=; b=Mqqsl+dd0C/T8J/oOFPZWuBXQwjO96q/i+daeGu55bsi86Ky560DCRdMd4v3YAmkOY 7j5CLGDGCWdOC3kGBUt49VRn2tnvAbhsbiR3bEumLmpIUI6xuLlKjDuMdtkR3X+ndUFR OjOCblpGHSjYSwCiBbzdc6phFivUA6b8GlVN45ZsnEz4RfSTCswiymjE+iwMMCjDYthO n6uB9CLjRwibYM/kzNtif7CSy0e7kFmPJaBquEDVbTGUYagGEp0wFLqeZlOXwV4wmpwD qu2U88Sp6U/DNpLeG+wfHJm18EHXoR+jpX9blD17WwSJTz4FFzWVeppeTG7D98yEbHpB Kqtw== X-Gm-Message-State: AG10YOQJMzTBOt5ZJD9DDqMGkBQqWKcZtszpu4LR5klYM4xU03TFIuLYZmyAg5sLJkc2Qw== X-Received: by 10.182.246.73 with SMTP id xu9mr3564664obc.20.1455749098125; Wed, 17 Feb 2016 14:44:58 -0800 (PST) Received: from [192.168.10.2] ([187.210.81.114]) by smtp.googlemail.com with ESMTPSA id d39sm2059831oic.0.2016.02.17.14.44.57 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 17 Feb 2016 14:44:57 -0800 (PST) Subject: Re: intr using Swap To: dweimer@dweimer.net References: <56C4AF81.3040202@motumweb.com> <87f6fb602e0ad11b7600c70a08d74c30@dweimer.net> <56C4C244.8070805@motumweb.com> <d6b6f3959b51a4ba3b8ab86de5931ae2@dweimer.net> Cc: stable@freebsd.org, owner-freebsd-stable@freebsd.org From: =?UTF-8?B?RWZyYcOtbiBEw6ljdG9y?= <efraindector@motumweb.com> Message-ID: <56C4F7E9.9090405@motumweb.com> Date: Wed, 17 Feb 2016 16:44:57 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: <d6b6f3959b51a4ba3b8ab86de5931ae2@dweimer.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>; List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Wed, 17 Feb 2016 22:44:59 -0000 El 17/02/2016 a las 01:15 p. m., dweimer escribió: > > They may not show as swapped unless the entire process is actually > swapped, which would be unlikely to occur. Personally I wouldn't worry > about it, the only thing I can think of is to restart processes one at > a time to see which one clears up the swap usage. Granted you may see > a little clear after each process. > > The more important task would be to determine what caused the memory > to run out in the first place, and decide if its going to be a > frequent enough occurrence to justify adding physical memory to the > system. > > There is likely some way to find out what is using it, but that is > beyond my knowledge. > > -- > Thanks, > Dean E. Weimer > http://www.dweimer.net/ The server has 64 GB of RAM, 40-45 GB are always inactive thats why I'm wondering why are the processes being swapped out. Thank you very much for your answers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d6b6f3959b51a4ba3b8ab86de5931ae2>