Re: Postgres Performance Tuning
От | tv@fuzzy.cz |
---|---|
Тема | Re: Postgres Performance Tuning |
Дата | |
Msg-id | 8b57d989ff79004f9159326f008abefb.squirrel@sq.gransy.com обсуждение исходный текст |
Ответ на | Postgres Performance Tuning (Adarsh Sharma <adarsh.sharma@orkash.com>) |
Ответы |
Re: Postgres Performance Tuning
|
Список | pgsql-performance |
> max_connections = 700 > shared_buffers = 4096MB > temp_buffers = 16MB > work_mem = 64MB > maintenance_work_mem = 128MB > wal_buffers = 32MB > checkpoint_segments = 32 > random_page_cost = 2.0 > effective_cache_size = 4096MB First of all, there's no reason to increase wal_buffers above 32MB. AFAIK the largest sensible value is 16MB - I doubt increasing it further will improve performance. Second - effective_cache_size is just a hint how much memory is used by the operating system for filesystem cache. So this does not influence amount of allocated memory in any way. > but Still Postgres Server uses Swap Memory While SELECT & INSERT into > database tables. Are you sure it's PostgreSQL. What else is running on the box? Have you analyzed why the SQL queries are slow (using EXPLAIN)? regards Tomas
В списке pgsql-performance по дате отправления: