| Simon Riggs 2005-10-27, 8:13 am |
| On Mon, 2005-10-24 at 13:08 -0500, Kevin Grittner wrote:
> Try getting lucky in google with "spinlock contention is greater"
Kevin's reference is actually to a Sybase manual page; very interesting.
This refers to the idea of subdividing the lock into may partitions.
That's already been discussed, but that is the next step beyond where we
are right now with a single cache but a much improved cache algorithm.
That technique is an algorithmic improvement rather than a hardware
specific improvment, which is what is required in the case we are
dealing with here.
Cool reference.
The idea of named caches is more familiar to me. Tuning for that is just
too hard and massively inflexible, so I don't think its the way anybody
really wants to go, but I hold the door open for anybody travelling that
way.
>
> How do other databases deal with this? I can't imagine we are the only
> ones. Are we doing something different than them?
I'm not sure the people qualified to answer that are able to do so. What
do other OSS projects do about this is more likely an answerable
question.
Best Regards, Simon Riggs
---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql
.org so that your
message can get through to the mailing list cleanly
|