From: | Jan Wieck <JanWieck(at)Yahoo(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Greg Stark <gsstark(at)mit(dot)edu>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [PATCHES] ARC Memory Usage analysis |
Date: | 2004-10-30 13:40:39 |
Message-ID: | 418399D7.6090204@Yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches pgsql-performance |
On 10/26/2004 1:53 AM, Tom Lane wrote:
> Greg Stark <gsstark(at)mit(dot)edu> writes:
>> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>>> Another issue is what we do with the effective_cache_size value once we
>>> have a number we trust. We can't readily change the size of the ARC
>>> lists on the fly.
>
>> Huh? I thought effective_cache_size was just used as an factor the cost
>> estimation equation.
>
> Today, that is true. Jan is speculating about using it as a parameter
> of the ARC cache management algorithm ... and that worries me.
If we need another config option, it's not that we are running out of
possible names, is it?
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Hallgren | 2004-10-30 16:03:56 | Problems using pgxs on Win32 |
Previous Message | Thomas Hallgren | 2004-10-30 10:35:01 | Signature change for SPI_cursor_open |
From | Date | Subject | |
---|---|---|---|
Next Message | a_ogawa | 2004-10-30 14:05:19 | Cache last known per-tuple offsets to speed long tuple access |
Previous Message | Peter Eisentraut | 2004-10-30 08:22:47 | Re: New Turkish translations for 7.4 branch + an update for 8.0 |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-10-30 16:53:36 | Re: [PATCHES] ARC Memory Usage analysis |
Previous Message | Tom Lane | 2004-10-29 14:37:23 | Re: determining max_fsm_pages |