Re: Postgres v MySQL 5.0
От | Chris Browne |
---|---|
Тема | Re: Postgres v MySQL 5.0 |
Дата | |
Msg-id | 60ejsbf2fv.fsf@dba2.int.libertyrms.com обсуждение исходный текст |
Ответ на | Re: Postgres v MySQL 5.0 ("Magnus Hagander" <mha@sollentuna.net>) |
Ответы |
Re: Postgres v MySQL 5.0
Re: Postgres v MySQL 5.0 |
Список | pgsql-advocacy |
usleepless@gmail.com writes: > i agree. lots of times postgresql is perceived as slow, because of > out-of-the-box configuration. most importantly, the memory > configuration. The defaults are a lot higher than they used to be, so I suspect that with 8.2, this may be less of an issue than it has traditionally been, particularly in that 8.2 uses various resources more effectively than has been true in the past. To wit... I did a "CVS HEAD" install the other day, to do some Slony-I testing. The *ONLY* config change I made was to change the port number. (Because the box already has 9 other production PG instances running on it! ;-)) The defaults for various interesting things were... max_connections = 100 shared_buffers = 32MB max_fsm_pages = 204800 The default work_mem was 1MB, which is arguably low, on a machine with 15GB of RAM :-). But frankly, I don't see any particular problem with the defaults. 32MB is *not* an over-tiny amount of shared memory; it's enough to be meaningful for more than merely a trivial workload. It looks like initdb is doing a better job of detecting system sizing than it used to, and the default numbers are no longer embarrassingly low. The 524K of yesteryear *was* embarrassing, but 32MB seems enough larger to me. -- (format nil "~S@~S" "cbbrowne" "linuxfinances.info") http://linuxdatabases.info/info/postgresql.html Rules of the Evil Overlord #207. "Employees will have conjugal visit trailers which they may use provided they call in a replacement and sign out on the timesheet. Given this, anyone caught making out in a closet while leaving their station unmonitored will be shot." <http://www.eviloverlord.com/>
В списке pgsql-advocacy по дате отправления: