2011/5/19 Robert Haas :
> On Thu, May 19, 2011 at 8:19 AM, Cédric Villemain
> wrote:
>> 2011/5/19 Robert Haas :
>>> On Tue, May 17, 2011 at 6:11 PM, Cédric Villemain
>>> wrote:
The point is to get ratio in cache, not the distribution of the data
in cache (pgfincore also allows you to se
On Thu, May 19, 2011 at 8:19 AM, Cédric Villemain
wrote:
> 2011/5/19 Robert Haas :
>> On Tue, May 17, 2011 at 6:11 PM, Cédric Villemain
>> wrote:
>>> The point is to get ratio in cache, not the distribution of the data
>>> in cache (pgfincore also allows you to see this information).
>>> I don't
2011/5/19 Robert Haas :
> On Tue, May 17, 2011 at 6:11 PM, Cédric Villemain
> wrote:
>> The point is to get ratio in cache, not the distribution of the data
>> in cache (pgfincore also allows you to see this information).
>> I don't see how a stable (a server in production) system can have its
>>
On Tue, May 17, 2011 at 6:11 PM, Cédric Villemain
wrote:
> The point is to get ratio in cache, not the distribution of the data
> in cache (pgfincore also allows you to see this information).
> I don't see how a stable (a server in production) system can have its
> ratio moving up and down so fast
2011/5/17 Robert Haas :
> On Sun, May 15, 2011 at 11:52 PM, Greg Smith wrote:
>> Cédric Villemain wrote:
>>>
>>> http://git.postgresql.org/gitweb?p=users/c2main/postgres.git;a=shortlog;h=refs/heads/analyze_cache
>>
>> This rebases easily to make Cedric's changes move to the end; I just pushed
>> a
On Sun, May 15, 2011 at 11:52 PM, Greg Smith wrote:
> Cédric Villemain wrote:
>>
>> http://git.postgresql.org/gitweb?p=users/c2main/postgres.git;a=shortlog;h=refs/heads/analyze_cache
>
> This rebases easily to make Cedric's changes move to the end; I just pushed
> a version with that change to
> h
Cédric Villemain wrote:
http://git.postgresql.org/gitweb?p=users/c2main/postgres.git;a=shortlog;h=refs/heads/analyze_cache
This rebases easily to make Cedric's changes move to the end; I just
pushed a version with that change to
https://github.com/greg2ndQuadrant/postgres/tree/analyze_cach
Hello
cache estimation and cache access cost are currently not accounted
explicitly: they have a cost associated with but no constants (other
than effective_cache_size but it has a very limited usage).
Every IO cost is build with a derivation of the seq_page_cost,
random_page_cost and the number