From: Thomas Ganss <tganss_at_t_dash_online_dot_de-remove-all-after-first-real-dash@yahoo.com>
To: pgsql-performance@postgresql.org
Subject: Re: Caching by Postgres
Date: Thu, 25 Aug 2005 14:23:49 +0100
Message-ID: <dekdcc$or1$02$1@news.t-online.com> (raw)
In-Reply-To: <20050824173055.GA11788@mark.mielke.cc>
References: <20050823171045.12112.qmail@web51309.mail.yahoo.com>
<20050823124323.710a9dd3.frank@wiles.org>
<430B6DE3.6040109@sun.com>
<deg68k$16gh$1@news.hub.org>
<430C7448.7030103@sun.com>
<20050824173055.GA11788@mark.mielke.cc>
> 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
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: pgsql-performance@postgresql.org
Cc: tganss_at_t_dash_online_dot_de-remove-all-after-first-real-dash@yahoo.com
Subject: Re: Caching by Postgres
In-Reply-To: <dekdcc$or1$02$1@news.t-online.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox