Received: from makus.postgresql.org ([98.129.198.125]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TQMJg-0007Fp-1I for pgsql-performance@postgresql.org; Mon, 22 Oct 2012 18:01:32 +0000 Received: from smtp2.peak6.com ([38.98.137.9]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TQMJe-0003Us-Ll for pgsql-performance@postgresql.org; Mon, 22 Oct 2012 18:01:31 +0000 X-AuditID: 0a02cb20-b7f726d000005255-8b-508589f9c9db Received: from sswchi5pcas2.peak6.net (sswchi5pcas2.peak6.net [10.100.13.24]) by smtp2.peak6.com (Symantec Messaging Gateway) with SMTP id 01.02.21077.9F985805; Mon, 22 Oct 2012 13:01:29 -0500 (CDT) Received: from [10.10.201.64] (10.10.201.64) by sswchi5pcas2.peak6.net (10.100.13.25) with Microsoft SMTP Server (TLS) id 14.2.247.3; Mon, 22 Oct 2012 13:01:28 -0500 Message-ID: <508589F8.7020808@optionshouse.com> Date: Mon, 22 Oct 2012 13:01:28 -0500 From: Shaun Thomas Reply-To: Organization: Peak6 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121011 Thunderbird/16.0.1 MIME-Version: 1.0 To: Claudio Freire CC: "pgsql-performance@postgresql.org" Subject: Re: Tons of free RAM. Can't make it go away. References: <508583E4.8080102@optionshouse.com> <5085873D.60400@optionshouse.com> In-Reply-To: Content-Type: text/plain; charset="ISO-8859-1"; format=flowed content-transfer-encoding: 7bit X-Originating-IP: [10.10.201.64] X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupnleLIzCtJLcpLzFFi42LhSuGV0P3Z2RpgMOe5gcWTX02sFtdnnmN2 YPLYOesuu8eFfdPYA5iiGhhtEvPy8ksSS1IVUlKLk22V/AtKMvPzij3yS4tTFVwyi5NzEjNz U4uUFDJTbJWMlRQKchKTU3NT80pslRILClLzUpTsuBQwgA1QWWaeQmpecn5KZl66rZJnsL+u hYWppa6hkl08MkjoZMn4+M2jYCNrxZS9DUwNjL+Yuxg5OSQETCQe/VjHDmGLSVy4t54NxBYS OMEo8W1BWBcjF5C9klHi/rs+JpAEr4C+xJNfj1hBbBYBVYl9K9+ygNhsAroSk/pXQDWrSPSd vQFWzy8gLLHvQxPYMlGBMInlOzdDzRGUODnzCViviIC2xJm7m8COYBbwlOg4tYoRxBYWsJfo +v+AGeKI24wSvWsglnEKBErMPvyYGaLBVuLCnOssELa8xPa3c5ghjlCVWNE8kQ3iMwWJ/1fe MU1gFJmFZPcsJO2zkLQvYGRexSheXJaYnJFpVlCcW1JgpFeQmphtppeXWrKJERTrTKcVdjBu 7rE6xCjAwajEw/vhXUuAEGtiWXFl7iFGCQ5mJRFe5YDWACHelMTKqtSi/Pii0pzU4kOMPsBA m8gsJZqcD0xDeSXxhsamBqaWpoam5qaGRjiElcR5J21rDBASSAcmn+zU1ILUIphxTBycUg2M XFIc+e4PdVbGJ/Dm9plvOtx9ZI1cbtZHGfd1S9t/xz3jrF773XBB2kTOdNEwoeCb/ziiJl/6 2ntlo/v9f57fpDZYqs8QdDpwMknlGf/FOdoZQuV31n6oiJlr5mr+8ee861e6frkY39Pt5zZf F6Vpem/9p2v/DoZE6276Y/XoxKlT7/IPrbTtUmIpzkg01GIuKk4EAHdN5OgiAwAA X-Pg-Spam-Score: -1.9 (-) X-Archive-Number: 201210/286 X-Sequence-Number: 48245 On 10/22/2012 12:53 PM, Claudio Freire wrote: > Did you check the kernel's zone_reclaim_mode ? It's currently set to 0, which as I'm led to believe, is the setting I want there. But here's something interesting: numactl --hardware available: 2 nodes (0-1) node 0 cpus: 0 2 4 6 8 10 12 14 16 18 20 22 node 0 size: 36853 MB node 0 free: 13816 MB node 1 cpus: 1 3 5 7 9 11 13 15 17 19 21 23 node 1 size: 36863 MB node 1 free: 751 MB node distances: node 0 1 0: 10 20 1: 20 10 Looks like CPU 0 is hoarding memory. :( -- Shaun Thomas OptionsHouse | 141 W. Jackson Blvd. | Suite 500 | Chicago IL, 60604 312-444-8534 sthomas@optionshouse.com ______________________________________________ See http://www.peak6.com/email_disclaimer/ for terms and conditions related to this email