From: | Jim Nasby <jim(at)nasby(dot)net> |
---|---|
To: | Dave Chinner <david(at)fromorbit(dot)com>, Marti Raudsepp <marti(at)juffo(dot)org> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, Kevin Grittner <kgrittn(at)ymail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Joshua Drake <jd(at)commandprompt(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Mel Gorman <mgorman(at)suse(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "lsf-pc(at)lists(dot)linux-foundation(dot)org" <lsf-pc(at)lists(dot)linux-foundation(dot)org>, Magnus Hagander <magnus(at)hagander(dot)net> |
Subject: | Re: [Lsf-pc] Linux kernel impact on PostgreSQL performance |
Date: | 2014-01-23 01:14:40 |
Message-ID: | 52E06D00.2060609@nasby.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 1/19/14, 5:51 PM, Dave Chinner wrote:
>> Postgres is far from being the only application that wants this; many
>> >people resort to tmpfs because of this:
>> >https://lwn.net/Articles/499410/
> Yes, we covered the possibility of using tmpfs much earlier in the
> thread, and came to the conclusion that temp files can be larger
> than memory so tmpfs isn't the solution here.:)
Although... instead of inventing new APIs and foisting this work onto applications, perhaps it would be better to modify tmpfs such that it can handle a temp space that's larger than memory... possibly backing it with X amount of real disk and allowing it/the kernel to decide when to passively move files out of the in-memory tmpfs and onto disk.
Of course that's theoretically what swapping is supposed to do, but if that's not up to the job...
--
Jim C. Nasby, Data Architect jim(at)nasby(dot)net
512.569.9461 (cell) http://jim.nasby.net
From | Date | Subject | |
---|---|---|---|
Next Message | KONDO Mitsumasa | 2014-01-23 01:28:39 | Re: Add min and max execute statement time in pg_stat_statement |
Previous Message | Jim Nasby | 2014-01-23 01:08:58 | Re: [Lsf-pc] Linux kernel impact on PostgreSQL performance |