On 23/08/12 11:06, Nick wrote:
I have a table with 40 million rows and haven't had any performance issues yet.
Are there any rules of thumb as to when a table starts getting too big?
For example, maybe if the index size is 6x the amount of ram, if the table is
10% of total disk space, etc?
I have a table with 40 million rows and haven't had any performance issues yet.
Are there any rules of thumb as to when a table starts getting too big?
For example, maybe if the index size is 6x the amount of ram, if the table is
10% of total disk space, etc?
--
Sent via pgsql-general
I have a table with 40 million rows and haven't had any performance issues yet. Are there any rules of thumb as to when a table starts getting too big? For example, maybe if the index size is 6x the amount of ram, if the table is 10% of total disk space, etc? -- My rule here is that a
On Wed, Aug 22, 2012 at 4:06 PM, Nick nboutel...@gmail.com wrote:
I have a table with 40 million rows and haven't had any performance issues
yet.
Are there any rules of thumb as to when a table starts getting too big?
For example, maybe if the index size is 6x the amount of ram, if the
On 2012-08-22, Nick nboutel...@gmail.com wrote:
I have a table with 40 million rows and haven't had any performance issues
yet.
Are there any rules of thumb as to when a table starts getting too big?
when you need to run a query that needs to fetch too many rows.
For example, maybe if the
In response to Martin French martin.fre...@romaxtech.com:
I have a table with 40 million rows and haven't had any performance
issues yet.
Are there any rules of thumb as to when a table starts getting too big?
For example, maybe if the index size is 6x the amount of ram, if the
On Wed, Aug 22, 2012 at 6:06 PM, Nick nboutel...@gmail.com wrote:
I have a table with 40 million rows and haven't had any performance issues
yet.
Are there any rules of thumb as to when a table starts getting too big?
For example, maybe if the index size is 6x the amount of ram, if the
On Thu, Aug 23, 2012 at 6:46 AM, Merlin Moncure mmonc...@gmail.com wrote:
On Wed, Aug 22, 2012 at 6:06 PM, Nick nboutel...@gmail.com wrote:
I have a table with 40 million rows and haven't had any performance issues
yet.
Are there any rules of thumb as to when a table starts getting too big?
Chris Travers chris.trav...@gmail.com writes:
On Thu, Aug 23, 2012 at 6:46 AM, Merlin Moncure mmonc...@gmail.com wrote:
Partitioning doesn't reduce index size -- it makes total index size
*bigger* since you have to duplicate higher nodes in the index --
unless you can exploit the table
I have a table with 40 million rows and haven't had any performance issues yet. Are there any rules of thumb as to when a table starts getting too big? For example, maybe if the index size is 6x the amount of ram, if the table is 10% of total disk space, etc?My rule here is
On Wed, Aug 22, 2012 at 4:06 PM, Nick nboutel...@gmail.com wrote:
I have a table with 40 million rows and haven't had any performance issues
yet.
Are there any rules of thumb as to when a table starts getting too big?
No. Assuming you decided it were too big, what could you do about it?
If
On Thu, Aug 23, 2012 at 6:37 AM, Bill Moran wmo...@potentialtech.com wrote:
In response to Martin French martin.fre...@romaxtech.com:
I have a table with 40 million rows and haven't had any performance
issues yet.
Are there any rules of thumb as to when a table starts getting too big?
On Thu, 23 Aug 2012 17:56:37 -0700 Jeff Janes jeff.ja...@gmail.com wrote:
On Thu, Aug 23, 2012 at 6:37 AM, Bill Moran wmo...@potentialtech.com wrote:
In response to Martin French martin.fre...@romaxtech.com:
I have a table with 40 million rows and haven't had any performance
issues
Hi,
On 23 August 2012 23:37, Bill Moran wmo...@potentialtech.com wrote:
And the advice I have along those lines is to establish now what
constitutes unacceptable performance, and put some sort of monitoring
and tracking in place to know what your performance degradation looks
like and
14 matches
Mail list logo
