From: | Richard Huxton <dev(at)archonet(dot)com> |
---|---|
To: | Marc Cousin <cousinmarc(at)gmail(dot)com> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Very big insert/join performance problem (bacula) |
Date: | 2009-07-14 08:15:21 |
Message-ID: | 4A5C3E99.5060100@archonet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Marc Cousin wrote:
>
>> Your effective_cache_size is really small for the system you seem to have -
>> its the size of IO caching your os is doing and uses no resources itself.
>> And 800MB of that on a system with that amount of data seems a bit unlikely
>> ;-)
>>
>> Using `free` you can see the amount of io caching your OS is doing atm. in
>> the 'cached' column.
>>
>> That possibly might tip some plans in a direction you prefer.
>>
>> What kind of machine are you running this on?
>
> I played with this parameter too, and it didn't influence the plan. Anyway, the
> doc says it's the OS cache available for one query,
No they don't. I'm guessing you're getting mixed up with work_mem.
> and there may be a lot of
> insert queries at the same time, so I chose to be conservative with this
> value. I tried it with 8GB too, the plans were the same.
>
> The OS cache is around 8-10GB by the way.
That's what you need to set effective_cache_size to then.
--
Richard Huxton
Archonet Ltd
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Huxton | 2009-07-14 08:23:25 | Re: Very big insert/join performance problem (bacula) |
Previous Message | Marc Cousin | 2009-07-14 05:54:38 | Re: Very big insert/join performance problem (bacula) |