Re: Now I am back, next thing. Final PGS tuning.
| От | David Wilson |
|---|---|
| Тема | Re: Now I am back, next thing. Final PGS tuning. |
| Дата | |
| Msg-id | e7f9235d0904080944u39d513edqa3d8e8e651c9e95f@mail.gmail.com обсуждение |
| Ответ на | Re: Now I am back, next thing. Final PGS tuning. (Jennifer Trey <jennifer.trey@gmail.com>) |
| Ответы |
Re: Now I am back, next thing. Final PGS tuning.
|
| Список | pgsql-general |
On Wed, Apr 8, 2009 at 12:24 PM, Jennifer Trey <jennifer.trey@gmail.com> wrote: > I think I might have misunderstood the effective cache size. Its measured in > 8kB blocks. So the old number 449697 equals 3.5 GB, which is quite much. > Should I lower this? I had plans to use 2.75GB max. Can I put 2.75GB there? > Should I leave it? The effective cache size setting is merely letting postgres know how much caching it can expect the OS to be doing. If you know that the OS isn't going to have more than 2.75 GB available for caching DB files, then by all means reduce it. The setting by itself doesn't affect postgres memory usage at all, though. -- - David T. Wilson david.t.wilson@gmail.com
В списке pgsql-general по дате отправления: