------=_Part_8150_15279041.1214867762706
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Yes, the server just does S, U, I and D.
The queries is pretty simples, don't have huge joins across tables...
In this server I have around 500 tables, the largest are:
9 millions tuples | 5 millions tuples
This server is our "authenticator"; the response is need to be
"imediatly".
Today, the monitoring of the server is done using the unix command:
loguptime
With the time we discovered that when loguptime is up than 1.0 the
response
begin to late, and the applications begin to take "Time-out".
2008/6/30 Tino Schwarze <postgresql@[EMAIL PROTECTED]
>:
> On Mon, Jun 30, 2008 at 04:01:14PM -0300, Rafael Domiciano wrote:
> > The Postgres version is 8.3.3 and I am using Fedora Core 8.
> > I have in the actual server around 70 connections the same time. I am
> > assigning for this 100.
>
> And what does the server do? Mainly SELECT / UPDATE / INSERT / DELETE,
> how is workload distributed, are queries very complex or pretty simple
> are there huge joins across many tables?
>
> How many tables do you have and what are the largest ones? Are we
talking
> about thousands of rows or millions or lots of millions?
>
> Tino.
>
> > > > Folks, I am configuring a new Postgres Server, that's gonna
> substitute
> > > the
> > > > critical server of the enterprise.
> > > > I have a good machine:
> > > > Quad-Core 2.5 Ghz
> > > > 4 Gb RAM
> > > > 1 Dedicated HD 300 Gb Sata for the PostgreSQL Directory
> > >
> > > If it's the "critical server", you'd want to use a RAID1 for the
disk
> so
> > > your server and data survives a harddisk crash.
> > >
> > > > My question is:
> > > > How much I could assign for the "Shared Buffers" parameter?
> > > >
> > > > The default assigned now is 24 Mb.
> > >
> > > That's rather low. I suppose, you may safely say 200Mb here (check
th=
at
> > > you don't run into OS limits, they might need raising). You may also
> > > want to increase work_mem, but it depends on what the DB does, how
ma=
ny
> > > concurrent connections you have etc. pp. maintenance_work_mem may
> safely
> > > be set rather high - it speeds up vacuum etc. and is only used
during
> > > such operations. Also look for effective_cache_size and
max_fsm_pages=
..
> > >
> > > BTW: What version are you going to use?
> > >
> > > Tino.
> > >
> > > --
> > > "What we nourish flourishes." - "Was wir n=E4hren erbl=FCht."
> > >
> > > www.craniosacralzentrum.de
> > > www.forteego.de
> > >
> > > --
> > > Sent via pgsql-admin mailing list (pgsql-admin@[EMAIL PROTECTED]
)
> > > To make changes to your subscription:
> > > http://www.postgresql.org/mailpref/pgsql-admin
> > >
>
> --
> "What we nourish flourishes." - "Was wir n=E4hren erbl=FCht."
>
> www.craniosacralzentrum.de
> www.forteego.de
>
> --
> Sent via pgsql-admin mailing list (pgsql-admin@[EMAIL PROTECTED]
)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-admin
>
------=_Part_8150_15279041.1214867762706
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Yes, the server just does S, U, I and D.<br>The queries is pretty simples,
=
don't have huge joins across tables...<br>In this server I have around
=
500 tables, the largest are:<br>9 millions tuples | 5 millions tuples<br>
<br>This server is our "authenticator"; the response is need to
b=
e "imediatly".<br>Today, the monitoring of the server is done
usi=
ng the unix command: loguptime<br>With the time we discovered that when
log=
uptime is up than 1.0 the response begin to late, and the applications
begi=
n to take "Time-out".<br>
<br><div class=3D"gmail_quote">2008/6/30 Tino Schwarze <<a
href=3D"mailt=
o:postgresql@[EMAIL PROTECTED]
"
target=3D"_blank">postgresql@[EMAIL PROTECTED]
>>:<br><blo=
ckquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204,
204,=
204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>On Mon, Jun 30, 2008 at 04:01:14PM -0300, Rafael Domiciano wrote:<br>
> The Postgres version is 8.3.3 and I am using Fedora Core 8.<br>
> I have in the actual server around 70 connections the same time. I
am<=
br>
> assigning for this 100.<br>
<br>
</div>And what does the server do? Mainly SELECT / UPDATE / INSERT /
DELETE=
,<br>
how is workload distributed, are queries very complex or pretty simple<br>
are there huge joins across many tables?<br>
<br>
How many tables do you have and what are the largest ones? Are we
talking<b=
r>
about thousands of rows or millions or lots of millions?<br>
<font color=3D"#888888"><br>
Tino.<br>
</font><div><div></div><div><br>
> > > Folks, I am configuring a new Postgres Server, that's
go=
nna substitute<br>
> > the<br>
> > > critical server of the enterprise.<br>
> > > I have a good machine:<br>
> > > Quad-Core 2.5 Ghz<br>
> > > 4 Gb RAM<br>
> > > 1 Dedicated HD 300 Gb Sata for the PostgreSQL Directory<br>
> ><br>
> > If it's the "critical server", you'd want to
us=
e a RAID1 for the disk so<br>
> > your server and data survives a harddisk crash.<br>
> ><br>
> > > My question is:<br>
> > > How much I could assign for the "Shared Buffers"
p=
arameter?<br>
> > ><br>
> > > The default assigned now is 24 Mb.<br>
> ><br>
> > That's rather low. I suppose, you may safely say 200Mb here
(=
check that<br>
> > you don't run into OS limits, they might need raising). You
m=
ay also<br>
> > want to increase work_mem, but it depends on what the DB does,
ho=
w many<br>
> > concurrent connections you have etc. pp. maintenance_work_mem
may=
safely<br>
> > be set rather high - it speeds up vacuum etc. and is only used
du=
ring<br>
> > such operations. Also look for effective_cache_size and
max_fsm_p=
ages.<br>
> ><br>
> > BTW: What version are you going to use?<br>
> ><br>
> > Tino.<br>
> ><br>
> > --<br>
> > "What we nourish flourishes." - "Was wir n=E4hren
=
erbl=FCht."<br>
> ><br>
> > <a href=3D"http://www.craniosacralzentrum.de"
target=3D"_blank">w=
ww.craniosacralzentrum.de</a><br>
> > <a href=3D"http://www.forteego.de"
target=3D"_blank">www.forteego=
..de</a><br>
> ><br>
> > --<br>
> > Sent via pgsql-admin mailing list (<a
href=3D"mailto:pgsql-admin@[EMAIL PROTECTED]
" target=3D"_blank">pgsql-admin@[EMAIL PROTECTED]
>)<br>
> > To make changes to your subscription:<br>
> > <a href=3D"http://www.postgresql.org/mailpref/pgsql-admin"
target=
=3D"_blank">http://www.postgresql.org/mailpref/pgsql-admin</a><br>
> ><br>
<br>
</div></div>--<br>
<div><div></div><div>"What we nourish flourishes." - "Was
wi=
r n=E4hren erbl=FCht."<br>
<br>
<a href=3D"http://www.craniosacralzentrum.de"
target=3D"_blank">www.cranios=
acralzentrum.de</a><br>
<a href=3D"http://www.forteego.de"
target=3D"_blank">www.forteego.de</a><br=
>
<br>
--<br>
Sent via pgsql-admin mailing list (<a
href=3D"mailto:pgsql-admin@[EMAIL PROTECTED]
" target=3D"_blank">pgsql-admin@[EMAIL PROTECTED]
>)<br>
To make changes to your subscription:<br>
<a href=3D"http://www.postgresql.org/mailpref/pgsql-admin"
target=3D"_blank=
">http://www.postgresql.org/mailpref/pgsql-admin</a><br>
</div></div></blockquote></div><br>
------=_Part_8150_15279041.1214867762706--
|
