Re: WIP patch for hint bit i/o mitigation

From: Greg Smith <greg(at)2ndQuadrant(dot)com>
To: Merlin Moncure <mmoncure(at)gmail(dot)com>
Cc: Amit Kapila <amit(dot)kapila(at)huawei(dot)com>, Atri Sharma <atri(dot)jiit(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: WIP patch for hint bit i/o mitigation
Date: 2012-11-21 21:30:05
Message-ID: 50AD47DD.10006@2ndQuadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 11/16/12 9:03 AM, Merlin Moncure wrote:
> Atri ran some quick n dirty tests to see if there
> were any regressions. He benched a large scan followed by vacuum. So
> far, results are inconclusive so better testing methodologies will
> definitely be greatly appreciated. One of the challenges with working
> in this part of the code is that it's quite difficult to make changes
> without impacting at least some workloads.

I'm adding something to pgbench-tools to test for some types of vacuum
regressions that I've seen before. And the checksum benchmarking I've
already signed up for overlaps with this one quite a bit. I'd suggest
reviewers here focus on code quality, correctness, and targeted
optimization testing. I'm working heavily on a larger benchmarking
framework that both this and checksums will fit into right now.

--
Greg Smith 2ndQuadrant US greg(at)2ndQuadrant(dot)com Baltimore, MD
PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Merlin Moncure 2012-11-21 21:56:02 Re: StrategyGetBuffer questions
Previous Message Alvaro Herrera 2012-11-21 21:29:20 Re: [v9.3] Extra Daemons (Re: elegant and effective way for running jobs inside a database)