From: | Mat Arye <mat(at)iobeam(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Table size for partitioned setup |
Date: | 2016-03-28 20:41:00 |
Message-ID: | CADsUR0ApxPOOgiZBkrW5U_t9cZk-gsCTGAV=N9qTCj7c28=vgg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi All,
I am writing a program that needs time-series-based insert mostly workload.
I need to make the system scaleable with many thousand of inserts/s. One of
the techniques I plan to use is time-based table partitioning and I am
trying to figure out how large to make my time tables.
Does anybody have any hints on optimal table sizes either in terms of rows
or in terms of size? Any rule of thumbs I can use for table size in
relation to amount of memory on the machine? Is the size of the index more
important than the size of the table (if queries mostly use indexes)?
Basically, I am asking for pointers about how to think about this problem
and any experiences people have had.
Thanks,
Mat
P.S. I am aware of limits listed here: http://www.postgresql.org/about/. I
am asking about practical size limits for performance consideration.
From | Date | Subject | |
---|---|---|---|
Next Message | Rob Sargent | 2016-03-28 20:49:21 | Re: Table size for partitioned setup |
Previous Message | Geoff Winkless | 2016-03-28 19:23:29 | More correlated (?) index woes |