Re: tuple data size and compression

From: Tom DalPozzo <t(dot)dalpozzo(at)gmail(dot)com>
To: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: tuple data size and compression
Date: 2016-12-16 16:45:45
Message-ID: CAK77FCSVNOS1B_ijgH1JtOe2Y+8AfTL=2a-+qUkZm18x0qyKRQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> Two questions:
>
> 1) Do you know what your data in the future is going to be?
>
> 2) Is a 100 byte bytea a realistic approximation of that data?
>
> wal_compression=off.
>>
>> --
> Adrian Klaver
> adrian(dot)klaver(at)aklaver(dot)com

Hi,
1) not precisely, but 10/100 million insertions per day. I can't know, it
depends on the success of all the system, whose the DB is a part only.
2) It will depend on my implementation which, in turn, depends on these
tests... Could be between 100 and 1000 bytes.
If 2) is 1000 random bytes, I saw that, with continuous archiveing (I'm
still evaluating if keeping it or not), I get 4KB/row IO write that,
in one year could become 70TB...
Anyway, I will perform my tests with realistic patterns
Regards
Pupillo

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Guyren Howe 2016-12-16 21:54:49 Love Your Database project — Thoughts on effectively handling constraints?
Previous Message Tom Lane 2016-12-16 16:28:29 Re: Allow login on slave only