Gregory Stark <stark@enterprisedb.com> writes:
> Tom Lane <tgl@sss.pgh.pa.us> writes:
>> In principle you should be able to adjust the constant so that vmstat
>> shows about 50% CPU busy, and then enabling fadvise should improve
>> matters significantly.
> I think in practice individual queries don't interleave much cpu with i/o
> work. A single random page fetch is 5ms which is an awful lot of cpu cycles to
> be sinking somewhere. In practice I think this is going to be single-digit
> percentages.
The point of the suggestion is to prove that the patch works as
advertised. How wide the sweet spot is for this test isn't nearly as
interesting as proving that there *is* a sweet spot. If you can't
find one it suggests that either the patch or the local posix_fadvise
doesn't work.
regards, tom lane
