Re: jsonb format is pessimal for toast compression
От | Arthur Silva |
---|---|
Тема | Re: jsonb format is pessimal for toast compression |
Дата | |
Msg-id | CAO_YK0W1pS35b6SkB08Pcqh28pikSagHWRGYrLDnGsQE03z8Eg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: jsonb format is pessimal for toast compression (Peter Geoghegan <pg@heroku.com>) |
Ответы |
Re: jsonb format is pessimal for toast compression
|
Список | pgsql-hackers |
It won't be faster by any means, but it should definitely be incorporated if any format changes are made (like Tom already suggested).
I think it's important we gather at least 2 more things before making any calls:
* Josh tests w/ cache aware patch, which should confirm cache aware is indeed prefered
* Tests with toast hacked to use lz4 instead, which might ease any decisions
--
Arthur Silva
Arthur Silva
On Wed, Aug 27, 2014 at 12:53 AM, Peter Geoghegan <pg@heroku.com> wrote:
On Tue, Aug 26, 2014 at 8:41 PM, Arthur Silva <arthurprs@gmail.com> wrote:I'm not surprised that it hasn't beaten HEAD. I haven't studied the
> The difference is small but I's definitely faster, which makes sense since
> cache line misses are probably slightly reduced.
> As in the previous runs, I ran the query a dozen times and took the average
> after excluding runs with a high deviation.
problem in detail, but I don't think that the "cache awareness" of the
new revision is necessarily a distinct advantage.
--
Peter Geoghegan
В списке pgsql-hackers по дате отправления: