Re: firebird X postgresql 8.1.2 windows, performance comparison

Поиск
Список
Период
Сортировка
Искать
От
David Brown
Тема
Re: firebird X postgresql 8.1.2 windows, performance comparison
Дата
Msg-id
4410BF88.5080001@bigpond.net.au
Ответ на
Список
Дерево обсуждения
firebird X postgresql 8.1.2 windows, performance comparison "andremachado" <andremachado@techforce.com.br>
Re: firebird X postgresql 8.1.2 windows, performance Scott Marlowe <smarlowe@g2switchworks.com>
Re: firebird X postgresql 8.1.2 windows, performance Alvaro Herrera <alvherre@commandprompt.com>
Re: firebird X postgresql 8.1.2 windows, performance Scott Marlowe <smarlowe@g2switchworks.com>
Re: firebird X postgresql 8.1.2 windows, performance Alvaro Herrera <alvherre@commandprompt.com>
Re: firebird X postgresql 8.1.2 windows, performance Tom Lane <tgl@sss.pgh.pa.us>
Re: firebird X postgresql 8.1.2 windows, performance comparison Andre Felipe Machado <andremachado@techforce.com.br>
Re: firebird X postgresql 8.1.2 windows, performance comparison Carlos Henrique Reimer <carlosreimer@yahoo.com.br>
Re: firebird X postgresql 8.1.2 windows, performance comparison PFC <lists@peufeu.com>
Re: firebird X postgresql 8.1.2 windows, performance comparison David Brown <time@bigpond.net.au>
firebird X postgresql 8.1.2 windows, performance comparison Andre Felipe Machado <andremachado@techforce.com.br>
Re: firebird X postgresql 8.1.2 windows, performance comparison "Jim C. Nasby" <jnasby@pervasive.com>
Re: firebird X postgresql 8.1.2 windows, performance comparison Chris Travers <chris@metatrontech.com>
Re: firebird X postgresql 8.1.2 windows, performance comparison Carlos Henrique Reimer <carlosreimer@yahoo.com.br>
Re: firebird X postgresql 8.1.2 windows, performance comparison "Joshua D. Drake" <jd@commandprompt.com>
Andre Felipe Machado wrote:

>It seems that Firebird windows can use adequately as much ram it finds
>and postgresql windows can not.
>  
>
PostgreSQL relies on the OS cache to utilize RAM. Make sure that most of 
the RAM is 'available' so Windows can do its thing.

effective_cache_size should be set correspondingly high - at least 65535.

shared_buffers should be as low as you can get away with (allowing for 
multiple users). 16384 is 12.5% of your RAM and far too high.

AFAIK, PostgreSQL still doesn't differentiate between index blocks and 
data blocks.

>work_mem reduced time almost 66%.
>But work_mem easily can exhaust ram with many users connected, as each
>connection query will use this amount of memory (if I can remember).
>How much it can grow at this 1 gbram win machine?
>  
>

work_mem has to be just big enough to allow hash joins to operate 
efficiently. This varies from query to query and can be set in your code 
accordingly. However, the 1024 default is just too low for most 
applications and you'll probably find even 4096 is a huge improvement. 
You need to find the minimum that delivers acceptable performance in 
most queries and boost it for selected queries as required.

BTW, which version of Firebird is this?
В списке pgsql-performance по дате отправления
От: Jan de Visser
Дата:
От: Casey Allen Shobe
Дата:
FAQ