3 ms·
Heroku has replied.. > Cache utilization talks about the working set size, yes. > > The database size typically means just the result of > pg_database_size(
by jaytaylor 14y ago
Heroku has replied..
> Cache utilization talks about the working set size, yes.
>
> The database size typically means just the result of
> pg_database_size() on your database (you can use the
> current_database() function as a shortcut). Note that this
> does include dead tuple bloat that is regularly cleaned
> up by Postgres autovacuum, so it's more of an estimate than
> a hard number.
- carsongross 14y agoRight, but that doesn't give you a good idea of how close your working set is to the max memory cache, unless your entire DB is active. I'll ping them again and ask if they've found a good way to measure this. It seems like this is the most important number to look at when scaling a heroku/postgres project.