| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: checkpointer continuous flushing |
| Date: | 2015-09-05 06:56:46 |
| Message-ID: | alpine.DEB.2.10.1509050852520.429@sto |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>>> I would be curious whether flushing helps, though.
>>
>> Yes, me too. I think we should try to reach on consensus for exact
>> scenarios and configuration where this patch('es) can give benefit or we
>> want to verify if there is any regression as I have access to this m/c for
>> a very-very limited time. This m/c might get formatted soon for some other
>> purpose.
>
> Yep, it would be great if you have time for a flush test before it
> disappears... I think it is advisable to disable the write cache as it may
> also hide the impact of flushing.
Still thinking... Depending on the results, it might be interesting to
have these tests run with the write cache enabled as well, to check how
much it interferes positively with performance.
I would guess "quite a lot".
--
Fabien.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2015-09-05 07:07:40 | Re: Fwd: Core dump with nested CREATE TEMP TABLE |
| Previous Message | Oskari Saarenmaa | 2015-09-05 06:47:07 | jsonb_concat: make sure we always return a non-scalar value |