pg.ddx.io pgsql-performance@postgresql.org mailing list archive
help / color / mirror / Atom feedfirst postgrreSQL tunning
4+ messages / 3 participants
[nested] [flat]
* first postgrreSQL tunning
@ 2005-01-06 13:19 Vinicius Caldeira Carvalho <vinicius.carvalho@squadra.com.br>
2005-01-06 15:52 ` Re: first postgrreSQL tunning Frank Wiles <frank@wiles.org>
0 siblings, 1 reply; 4+ messages in thread
From: Vinicius Caldeira Carvalho @ 2005-01-06 13:19 UTC (permalink / raw)
To: pgsql-performance
Hi there! I'm doing my first tunning on my postgreSQL, my server is for
a small app, largest table shall never exceed 10k rows, and less than 1k
transactions/day. So I don't think I should run out of resources. The
machine is a Fedora Core 3.0 with 1gb ran and kernel 2.6. I'm thinking
in having 50 connections limit, so besides semaphores should I do
anything special on kernel parameters. The app is so small that during
late night time almost no one will access so, I'm thinking in full
vacuuming it every day at 1:00AM.
Any tips are very very welcome :D
Thanks all
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: first postgrreSQL tunning
2005-01-06 13:19 first postgrreSQL tunning Vinicius Caldeira Carvalho <vinicius.carvalho@squadra.com.br>
@ 2005-01-06 15:52 ` Frank Wiles <frank@wiles.org>
0 siblings, 0 replies; 4+ messages in thread
From: Frank Wiles @ 2005-01-06 15:52 UTC (permalink / raw)
To: Vinicius Caldeira Carvalho <vinicius.carvalho@squadra.com.br>; +Cc: pgsql-performance
On Thu, 06 Jan 2005 11:19:51 -0200
Vinicius Caldeira Carvalho <vinicius.carvalho@squadra.com.br> wrote:
> Hi there! I'm doing my first tunning on my postgreSQL, my server is
> for a small app, largest table shall never exceed 10k rows, and less
> than 1k transactions/day. So I don't think I should run out of
> resources. The machine is a Fedora Core 3.0 with 1gb ran and kernel
> 2.6. I'm thinking in having 50 connections limit, so besides
> semaphores should I do anything special on kernel parameters. The app
> is so small that during late night time almost no one will access so,
> I'm thinking in full vacuuming it every day at 1:00AM.
>
> Any tips are very very welcome :D
You'll want to tune shared_buffers and sort_mem. Possibly also
effective_cache_size. It really depends on your system.
Having tuned a ton of apps to work with PostgreSQL what I usually
do is write a small script that does the major resource intensive
queries on the database and time it. Tweak a PostgreSQL parameter
and re-run, wash, rinse, repeat until I get what I believe is the
best performance I can.
---------------------------------
Frank Wiles <frank@wiles.org>
http://www.wiles.org
---------------------------------
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: first postgrreSQL tunning
@ 2005-01-06 13:34 Merlin Moncure <merlin.moncure@rcsonline.com>
2005-01-06 13:46 ` Re: first postgrreSQL tunning Vinicius Caldeira Carvalho <vinicius.carvalho@squadra.com.br>
0 siblings, 1 reply; 4+ messages in thread
From: Merlin Moncure @ 2005-01-06 13:34 UTC (permalink / raw)
To: Vinicius Caldeira Carvalho <vinicius.carvalho@squadra.com.br>; +Cc: pgsql-performance
> Hi there! I'm doing my first tunning on my postgreSQL, my server is
for
> a small app, largest table shall never exceed 10k rows, and less than
1k
> transactions/day. So I don't think I should run out of resources. The
> machine is a Fedora Core 3.0 with 1gb ran and kernel 2.6. I'm thinking
> in having 50 connections limit, so besides semaphores should I do
> anything special on kernel parameters. The app is so small that during
> late night time almost no one will access so, I'm thinking in full
> vacuuming it every day at 1:00AM.
The biggest danger with small databases is it's easy to become
overconfident...writing poor queries and such and not properly indexing.
50 users can hit your system pretty hard if they all decide to do
something at once. Aside from that, just remember to bump up work_mem a
bit for fast joining.
Your application may be small, but if it is written well and works, it
well inevitably become larger and more complex, so plan for the future
:)
Merlin
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: first postgrreSQL tunning
2005-01-06 13:34 Re: first postgrreSQL tunning Merlin Moncure <merlin.moncure@rcsonline.com>
@ 2005-01-06 13:46 ` Vinicius Caldeira Carvalho <vinicius.carvalho@squadra.com.br>
0 siblings, 0 replies; 4+ messages in thread
From: Vinicius Caldeira Carvalho @ 2005-01-06 13:46 UTC (permalink / raw)
To: pgsql-performance
Merlin Moncure wrote:
>>Hi there! I'm doing my first tunning on my postgreSQL, my server is
>>
>>
>for
>
>
>>a small app, largest table shall never exceed 10k rows, and less than
>>
>>
>1k
>
>
>>transactions/day. So I don't think I should run out of resources. The
>>machine is a Fedora Core 3.0 with 1gb ran and kernel 2.6. I'm thinking
>>in having 50 connections limit, so besides semaphores should I do
>>anything special on kernel parameters. The app is so small that during
>>late night time almost no one will access so, I'm thinking in full
>>vacuuming it every day at 1:00AM.
>>
>>
>
>The biggest danger with small databases is it's easy to become
>overconfident...writing poor queries and such and not properly indexing.
>50 users can hit your system pretty hard if they all decide to do
>something at once. Aside from that, just remember to bump up work_mem a
>bit for fast joining.
>
>Your application may be small, but if it is written well and works, it
>well inevitably become larger and more complex, so plan for the future
>:)
>
>Merlin
>
>
>---------------------------(end of broadcast)---------------------------
>TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
>
>
>
>
Thanks Merlin, besides what I said of tunning anything else I should
care looking at?
^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2005-01-06 15:52 UTC | newest]
Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2005-01-06 13:19 first postgrreSQL tunning Vinicius Caldeira Carvalho <vinicius.carvalho@squadra.com.br>
2005-01-06 15:52 ` Frank Wiles <frank@wiles.org>
2005-01-06 13:34 Re: first postgrreSQL tunning Merlin Moncure <merlin.moncure@rcsonline.com>
2005-01-06 13:46 ` Vinicius Caldeira Carvalho <vinicius.carvalho@squadra.com.br>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox