From: | "Qingqing Zhou" <zhouqq(at)cs(dot)toronto(dot)edu> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: SHM_LOCK under Linux ... do we use this? |
Date: | 2005-08-18 09:14:02 |
Message-ID: | de1jlh$22k1$1@news.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
""Marc G. Fournier"" <scrappy(at)postgresql(dot)org> writes
>
> I've done a grep through the code, to see if its something that we do use,
and
> it doesn't seem to come back with anything ... I believe its considered
> common knowledge that 'swapping' for a database is evil, so am wondering
> if there is some way that we can make use of this to help reduce/eliminate
> that from happening?
>
There are some similar flags in other OS could help us to keep the memory
resident in. However, it is not always a net win if we force it. This is
because other parts of the system (like fork a process) may need memory, so
the OS will pick up the "coldest" memory to be swapped. If we have already
use our memory intensively, I don't think we will be swapped. On the
contrary, if we force OS not to swap some memory, we may get other penalties
like our processes have to be sarcrificed.
Regards,
Qingqing
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2005-08-18 12:18:32 | Re: [PERFORM] bitmap scan issues 8.1 devel |
Previous Message | Djoerd Hiemstra | 2005-08-18 08:50:16 | SQL/XML extension |