Re: [PERFORM] Caching by Postgres

2005-08-26 Thread Thomas Ganss



The first, to always remember - is that the move from 64-bits to
32-bits doesn't come for free. In a real 64-bit system with a
64-bit operating system, and 64-bit applications, pointers are
now double their 32-bit size. This means more bytes to copy around
memory, and in an extreme case, has the potential to approach
halfing both the memory latency to access many such pointers from
RAM, and half the effective amount of RAM. In real world cases,
not everything is a pointer, so this sort of performance degradation
is doubtful - but it is something to keep in mind.

In addition to the above it lessens the effects of the CPU cache, so be 
sure to take the larger cached versions if you have structures needing 
to fit into the cache...


my 0.02 EUR

thomas

---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster


Re: [PERFORM] multi billion row tables: possible or insane?

2005-03-01 Thread Thomas Ganss
Ramon Bastiaans schrieb:
My currect estimate is that I have to store (somehow) 
around 1 billion values each month (possibly more).
You should post the actual number or power of ten,
since "billion" is not always interpreted the same way...
rgds
thomas
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
  http://www.postgresql.org/docs/faq