From: | Casey Duncan <casey(at)pandora(dot)com> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | pgsql-hackers(at)postgresql(dot)org, ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> |
Subject: | Re: Questions about guc units |
Date: | 2006-09-25 23:44:31 |
Message-ID: | 65B4CBDD-B670-4AD4-B331-AF56FCA391DD@pandora.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
On Sep 25, 2006, at 1:03 AM, Peter Eisentraut wrote:
> Am Montag, 25. September 2006 04:04 schrieb ITAGAKI Takahiro:
>> #shared_buffers = 32000kB # min 128kB or max_connections*16kB
>> #temp_buffers = 8000kB # min 800kB
>> #effective_cache_size = 8000kB
>>
>> Are there any reasons to continue to use 1000-unit numbers?
>> Megabyte-unit
>> (32MB and 8MB) seems to be more friendly for users. It increases some
>> amount of values (4000 vs. 4096), but there is little in it.
>
> The reason with the shared_buffers is that the detection code in
> initdb has
> 400kB as minimum value, and it would be pretty complicated to code the
> detection code to handle both kB and MB units. If someone wants to
> try it,
> though, please go ahead.
Seems like the unit used for shared_buffers (and others) should be
megabytes then with a minimum of 1 (or more). Is less than 1MB
granularity really useful here? On modern hardware 1MB of RAM is in
the noise.
-Casey
From | Date | Subject | |
---|---|---|---|
Next Message | Pang Zaihu | 2006-09-26 01:09:33 | Re: String Similarity |
Previous Message | Peter Eisentraut | 2006-09-25 23:20:22 | Re: Questions about guc units |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Treat | 2006-09-26 00:52:49 | minor editorial of tsearch2 readme |
Previous Message | Peter Eisentraut | 2006-09-25 23:20:22 | Re: Questions about guc units |