agora inbox for [email protected]  

help / color / mirror / Atom feed

From: Jim Nasby <[email protected]>
To: Petr Jelinek <[email protected]>
To: Andres Freund <[email protected]>
To: [email protected]
To: Robert Haas <[email protected]>
Cc: Bruce Momjian <[email protected]>
Cc: Sawada Masahiko <[email protected]>
Cc: Greg Stark <[email protected]>
Cc: PostgreSQL-development <[email protected]>
Cc: Jeff Janes <[email protected]>
Subject: Re: Reducing tuple overhead
Date: Thu, 23 Apr 2015 14:33:48 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
List-Unsubscribe: <mailto:[email protected]?body=unsub%20pgsql-hackers>

On 4/23/15 11:45 AM, Petr Jelinek wrote:
> On 23/04/15 18:24, Andres Freund wrote:
>> Whether that's feasible complexity wise is debatable, but it's certainly
>> possible.
>>
>>
>> I do wonder what, in realistic cases, is actually the bigger contributor
>> to the overhead. The tuple header or the padding we liberally add in
>> many cases...
>>
>
> The logical ordering patch + auto optimizations of column layout on
> table creation/rewrite might help partially there.
>
> But what seems to be clear is that we need more in depth analysis of
> what really contributes most to the tuple size in various use-cases and
> then we can debate what we can do about it.

Also, what Robert posted was that while we started at something like 
15%-30% larger, we ended the test at 80% larger. That makes me think 
that the bigger win is not in reducing tuple size but tackling bloat.
-- 
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com


-- 
Sent via pgsql-hackers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

view thread (27+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Reducing tuple overhead
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox