Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Tse2j-0006FW-OC for pgsql-performance@arkaria.postgresql.org; Tue, 08 Jan 2013 18:36:57 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1Tse2i-0002uR-If for pgsql-performance@arkaria.postgresql.org; Tue, 08 Jan 2013 18:36:56 +0000 Received: from magus.postgresql.org ([87.238.57.229]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Tse2h-0002uL-IK for pgsql-performance@postgresql.org; Tue, 08 Jan 2013 18:36:55 +0000 Received: from smtp.optionshouse.com ([38.98.137.6] helo=smtp.peak6.com) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Tse2e-0002YK-QW for pgsql-performance@postgresql.org; Tue, 08 Jan 2013 18:36:55 +0000 X-AuditID: 0a64cb20-b7f466d0000073cd-13-50ec67435f93 Message-ID: <50EC6742.4090303@optionshouse.com> Date: Tue, 8 Jan 2013 12:36:50 -0600 From: Shaun Thomas Reply-To: Organization: Peak6 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Scott Marlowe CC: Midge Brown , Subject: Re: Two Necessary Kernel Tweaks for Linux Systems References: <50E4AAB1.9040902@optionshouse.com> <50EC6549.3090503@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+NgFmpgleLIzCtJLcpLzFFi42LhSuGV0HVOfxNgMGmPksWyX1YW12eeY7ZY 9uk8owOzx85Zd9k9Luybxu6x/v9i1gDmqAZGm8S8vPySxJJUhZTU4mRbJf+Cksz8vGKP/NLi VAWXzOLknMTM3NQiJYXMFFslYyWFgpzE5NTc1LwSW6XEgoLUvBQlOy4FDGADVJaZp5Cal5yf kpmXbqvkGeyva2FhaqlrqGQXjwwSOlkyZq/exVzwjLnia/M1tgbGFuYuRk4OCQETiYMLFrFD 2GISF+6tZwOxeQX0JRqOLgOLswioSDSdmAhmswnoSkzqXwFWIwQU7zt7gwnE5hcQltj3oQls pqhAgMTiJefYIeYISpyc+YQFxBYR0JZ49OY6I4jNLOAtMWvCAbBeYQEXiWtNq4BmcgHNPMwo 0fj0LNggToFAie5Xx1kgGmwlLsy5DmXLS2x/O4cZ4ghViRXNE9kgHlCQ+H/lHdMERqFZSHbP QtI+C0n7AkbmVYzixWWJyRmZpgXFuSUFRnoFqYnZZnp5qSWbGMHRfFphB+P3TqtDjAIcjEo8 vA2JrwOEWBPLiitzDzFKcDArifDe9X4TIMSbklhZlVqUH19UmpNafIjRBxhoE5mlRJPzgYkm ryTe0NjUwNTS1NDU3NTQCIewkjhvaOiiACGBdGAyyU5NLUgtghnHxMEp1cDoZ/1l2iaht+/c dm5ZvbBnj+HtaLud3j+uXI5+quV62vqUXuErCYb8ZYmz5X4z6/487TDFKnZ5+XvbV7+esWbY vV2+Lv573SNJrdUZbHffW64S/iecv1xeZ1nYNL1pSRxsNxkr7qbbi0hXZQQbLnt7jSFT8fH/ 7UxRJdyufLd9nOQSE3Zs+TFTiaU4I9FQi7moOBEADk+cGRMDAAA= 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 01/08/2013 12:31 PM, Scott Marlowe wrote: > What's the comparison of these settings versus say going to the NOP > scheduler? Assuming you actually meant NOP and not the NOOP I/O scheduler, I don't know. These CPU scheduler tweaks are all I could dig up, and googling for NOP by itself or combined with Linux terms is tremendously unhelpful. -- 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 -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance