Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WvU53-0007Mk-3k for pgsql-performance@arkaria.postgresql.org; Fri, 13 Jun 2014 16:11:53 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1WvU52-0003Ev-Ab for pgsql-performance@arkaria.postgresql.org; Fri, 13 Jun 2014 16:11:52 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1WvU51-0003Eh-25 for pgsql-performance@postgresql.org; Fri, 13 Jun 2014 16:11:51 +0000 Received: from smtp2.peak6.com ([38.98.137.9]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WvU4x-0003fv-6m for pgsql-performance@postgresql.org; Fri, 13 Jun 2014 16:11:49 +0000 X-AuditID: 0a02cb20-f798c6d000007a0a-70-539b22c1954f Received: from sswchi5pcas1.peak6.net (Unknown_Domain [10.100.13.22]) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate) by smtp2.peak6.com (Symantec Messaging Gateway) with SMTP id 4C.1E.31242.1C22B935; Fri, 13 Jun 2014 11:11:45 -0500 (CDT) Received: from [10.10.220.56] (10.10.220.56) by sswchi5pcas1.peak6.net (10.100.13.25) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 13 Jun 2014 11:11:44 -0500 Message-ID: <539B22BD.6010803@optionshouse.com> Date: Fri, 13 Jun 2014 11:11:41 -0500 From: Shaun Thomas User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Tim Kane , Brio , Subject: Re: postgres files in use not staying in linux file cache References: <53977376.3040406@optionshouse.com> In-Reply-To: Content-Type: text/plain; charset="UTF-8"; format=flowed content-transfer-encoding: 8bit X-Originating-IP: [10.10.220.56] X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrAIsWRmVeSWpSXmKPExsXClcIrpntQaXawweWtqhazrt5lsbg+8xyz xZanvA7MHjtn3WX3uLBvGnsAU1QDo01iXl5+SWJJqkJKanGyrZJ/QUlmfl6xR35pcaqCS2Zx ck5iZm5qkZJCZoqtkrGSQkFOYnJqbmpeia1SYkFBal6Kkh2XAgawASrLzFNIzUvOT8nMS7dV 8gz217WwMLXUNVSyi0cGCZ0sGQfmv2AqOMRbserRW+YGxntcXYycHBICJhJfJm1khrDFJC7c W8/WxcjFISQwl0li6ZvvLBDOSkaJhx9usoJU8QroSyw8foYdxGYRUJXYcO8jWJxNQFdiUv8K NhBbVCBM4uPRdWwQ9YISJ2c+YQGxRQRSJF7NX8cEYgsL+Ei8X97OBLFgBqNE67/3YAlOAQOJ DRdmgzUwC1hILH5zkB3Clpdo3job7FQhoMUrmicCLeAAOlsB6OzUCYyCs5Csm4WkexaS7gWM zKsYxYvLEpMzMs0KinNLCoz0ClITs8308lJLNjGCopXptMIOxs09VocYBTgYlXh4N/yYGSzE mlhWXJl7iFGCg1lJhJdXZnawEG9KYmVValF+fFFpTmrxIUYfYHhMZJYSTc4HJpK8knhDY1MD U0tTQ1NzU0MjHMJK4rxHWuKChQTSgWkjOzW1ILUIZhwTB6dUA2Pb3dWtWne+ciscmf3OV+rI 73le8oe/snLutw8Q/pqtkfdlQazKawbpC0+azVk1N/GfXCrLoPihQvjw4w9dzs7ZR61UDr1a 88Bg5cPwyYdPPwhVebFnShd7+ZSE//8z3Kwf5i9gj9v086nulltnWxo1zyu+FFtl5TH10xUZ kf22S78ny246kvFXiaU4I9FQi7moOBEAYtjIhgMDAAA= X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org On 06/13/2014 02:19 AM, Tim Kane wrote: > I ask because I’ve just read your statement above about 3.2 being > pants-on-head, and having had more luck with 3.8 and above – despite > most installations being on much older (2.6.19) kernels (as per the > thread). Well, the issue is that the 3.2 kernel was a huge departure from the 2.6 tree that most people are still using. Thanks to RHEL, CentOS and their ilk, the 2.6 tree has had a much longer lifetime than it probably should have. As a result, the newer kernels haven't had sufficient real-world server testing. With 3.2 being the first of those, it was a bit wonky, to be honest. The new CPU scheduler didn't have enough knobs, and the knobs that *were* there, were set more appropriately for desktop use. The memory manager was a train wreck and has been patched numerous times with rather sweeping changes since. For a while, there was even a bug at how system load was calculated that caused it to be off by an order of magnitude or more based on process switching activity. The overall situation has improved significantly, as has the development momentum. It's extremely difficult to say which kernel versions have more risk than others, since no kernel seems to be around for more than a month or two before the next one comes out. My opinion has been to get on the latest stable kernel for the distribution, and ignore everything else. For Ubuntu 12.04.4 LTS, that's 3.11. Our systems are definitely much happier since the upgrade, but the plural of anecdote is not data. :) -- Shaun Thomas OptionsHouse, LLC | 141 W. Jackson Blvd. | Suite 800 | Chicago IL, 60604 312-676-8870 sthomas@optionshouse.com ______________________________________________ See http://www.peak6.com/email_disclaimer/ for terms and conditions related to this email -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance