Re: Re[2]: [HACKERS] Re: [Lsf-pc] Linux kernel impact on PostgreSQL performance (summary v2 2014-1-17)

From: Claudio Freire <klaussfreire(at)gmail(dot)com>
To: Миша Тюрин <tmihail(at)bk(dot)ru>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, "lsf-pc(at)lists(dot)linux-foundation(dot)org" <lsf-pc(at)lists(dot)linux-foundation(dot)org>
Subject: Re: Re[2]: [HACKERS] Re: [Lsf-pc] Linux kernel impact on PostgreSQL performance (summary v2 2014-1-17)
Date: 2014-01-21 20:27:18
Message-ID: CAGTBQpZON6N99BbTArTEBm9A549koSn70a+EsxLonbtJh6asRA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jan 21, 2014 at 5:01 PM, Миша Тюрин <tmihail(at)bk(dot)ru> wrote:
> And does anyone know how mysql-innodb guys are getting with similar issues?

I'm no innodb dev, but from managing mysql databases, I can say that
mysql simply eats all the RAM the admin is willing to allocate for the
DB, and is content with the page cache almost not working.

IOW: mysql manages its own cache and doesn't need or want the page
cache. That *does* result in terrible performance when I/O is needed.
Some workloads are nigh-impossible to optimize with this scheme.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2014-01-21 20:29:08 Re: ALTER SYSTEM SET typos and fix for temporary file name management
Previous Message Alvaro Herrera 2014-01-21 20:21:50 Re: Closing commitfest 2013-11