From: | Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com> |
---|---|
To: | Gregory Stark <stark(at)enterprisedb(dot)com> |
Cc: | Simon Riggs <simon(at)2ndQuadrant(dot)com>, Greg Smith <gsmith(at)gregsmith(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Initial prefetch performance testing |
Date: | 2008-09-22 18:15:55 |
Message-ID: | 48D7E0DB.4040109@cheapcomplexdevices.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Gregory Stark wrote:
> Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
>> I'm not in favour of introducing the concept of spindles....
>
> In principle I quite strongly disagree with this....
> Number of blocks to prefetch is an internal implementation detail that the DBA
> has absolutely no way to know what the correct value is.
Even more often on systems I see these days, "spindles"
is an implementation detail that the DBA has no way to know
what the correct value is.
For example, on our sites hosted with Amazon's compute cloud (a great
place to host web sites), I know nothing about spindles, but know
about Amazon Elastic Block Store[2]'s and Instance Store's[1]. I
have some specs and are able to run benchmarks on them; but couldn't
guess how many spindles my X% of the N-disk device that corresponds
to. For another example, some of our salesguys with SSD drives
have 0 spindles on their demo machines.
I'd rather a parameter that expressed things more in terms of
measurable quantities -- perhaps seeks/second? perhaps
random-access/sequential-access times?
[1] http://www.amazon.com/gp/browse.html?node=201590011
[2] http://www.amazon.com/b/ref=sc_fe_c_0_201590011_1?ie=UTF8&node=689343011&no=201590011&me=A36L942TSJ2AJA
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2008-09-22 18:19:02 | Re: get_relation_stats_hook() |
Previous Message | Simon Riggs | 2008-09-22 18:14:18 | Re: Initial prefetch performance testing |