From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
---|---|
To: | neto brpr <netobrpr(at)gmail(dot)com> |
Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Cost Model |
Date: | 2017-12-20 18:35:23 |
Message-ID: | 20171220183523.ymmcykkbervcghpe@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
neto brpr wrote:
> Dear David
> I have read documentation that you send, but it has only sequential page
> cost and random page cost parameters. What I need, would be a model of
> custo for Differentiate Read/Write (sequential and random), because in SSDs
> the reads and writes have different costs.
I don't think it matters. I mean, differentiating seq/random read
speeds can make the planner choose one plan type over another depending
on how much each plan intends to read randomly or sequentially. But why
does it matter if one write is 360x as expensive as one read? No plan
is going to change usefully because of that, because you can't turn one
write into 360 reads or even 100000000 reads.
If you said "writes of type X are 100 times as fast as writes of type
Y", then some useful cost model could perhaps be developed. But that's
not what you're saying.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2017-12-20 18:37:40 | Re: Cost Model |
Previous Message | neto brpr | 2017-12-20 18:26:00 | Re: Cost Model |