Re: Measuring database IO for AWS RDS costings

From: David Osborne <david(at)qcode(dot)co(dot)uk>
To: Guillaume Lelarge <guillaume(at)lelarge(dot)info>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Measuring database IO for AWS RDS costings
Date: 2014-08-14 09:21:19
Message-ID: CAKmpXCeJMJ-VsisJe8_Cc2d3soKH4VvgZmUz5oTquxcVvK7bkw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

>
> You're right that they are 8kB blocks (by default). But it's not read from
> disk, is more "postgresql asks the OS to give it the blocks". They may come
> from the disk, but they also may come from the OS disk cache. You can't
> find actual disk reads and writes from PostgreSQL.
>
Thanks.
That makes it a bit tricky then.
So my best bet might be running iostat on the physical server and
calculating Blk_read + Blk_wrtn for a period (4kb blocks in this case) and
using that to estimate how many 16kb IO's that might translate to on AWS's
RDS service for a month.

--
David

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message John Scalia 2014-08-14 13:30:13 Re: pg_upgrade hangs
Previous Message Bruce Momjian 2014-08-14 02:48:21 Re: pg_upgrade hangs