Re: How to reduce impact of a query.
От | Isak Hansen |
---|---|
Тема | Re: How to reduce impact of a query. |
Дата | |
Msg-id | 6b9e1eb20811170454g1b96e8ffp55585f54d99de7e8@mail.gmail.com обсуждение исходный текст |
Ответ на | How to reduce impact of a query. (Howard Cole <howardnews@selestial.com>) |
Список | pgsql-general |
On Mon, Nov 17, 2008 at 1:15 PM, Howard Cole <howardnews@selestial.com> wrote: > Hi, > > I am running multiple 8.2 databases on a not-so-powerful W2K3 server - and > it runs great - for the majority of time. However I have some monster > tsearch queries which take a lot of processing and hog system resources - > especially disk. > > I am not concerned with the amount of time or speed of the tsearch2 query, > which is doing a lot of work, all I need to do is make sure that the query > does not impact all other databases and queries running on the same machine. > > The machine in question is a 1GB Ram, AMD 64 with Raid 1 Sata disks. Non > standard parts of my postgresql.conf are as follows: > max_connections=100 > shared_buffers=128MB > work_mem=4MB > maintenance_work_mem=256MB > max_fsm_pages=204800 > max_fsm_relations=1500 > > Any tips appreciated. Not directly related to your question, but if effective_cache_size hasn't been changed from the default, adjusting it could improve overall performance a fair bit. Regards, Isak
В списке pgsql-general по дате отправления: