123 reputation
14
bio website
location
age
visits member for 3 years, 4 months
seen Aug 29 '13 at 7:05

Sep
9
awarded  Enthusiast
May
13
comment Option shared_buffers in PostgreSQL
Sorry, I forgot to comment: debug_assertions = off
May
13
awarded  Scholar
May
13
accepted Option shared_buffers in PostgreSQL
May
13
comment Option shared_buffers in PostgreSQL
Thanks for your answer. All tests were performed with and without autovacuum, and each test was run 3 times (SETTIMES = 3 in the config file of pgbench-tools). With shared_buffers = 128 Mb, the result are similar to default configuration, but when I increase this option to 256 Mb, the performance is more lower with scale = 100 or greater.
May
13
awarded  Supporter
May
9
awarded  Editor
Apr
30
comment Option shared_buffers in PostgreSQL
Hi Eelke, in an earlier test to the two tests that indicated in the first message, the memory configuration was: shared_buffers = 512 MB; maintenance_work_mem = 8MB; effective_cache_size = 1GB; work_mem = 2MB; And the results were similar, even slightly worse. For that reason, I did tests changing options one by one, to know what was the cause of poor performance. And "the winner" is shared_buffers...
Apr
30
comment Option shared_buffers in PostgreSQL
Hi Idleyoungman, yes the shmmax value is higher (536870912). If I had a smaller value, PostgreSQL will not start.
Apr
30
awarded  Student
Apr
29
asked Option shared_buffers in PostgreSQL