| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | AMatveev(at)bitec(dot)ru |
| Cc: | Achilleas Mantzios <achill(at)matrix(dot)gatewaynet(dot)com>, "pgsql-general(at)postgresql(dot)org >> PG-General Mailing List" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Memory usage per session |
| Date: | 2016-07-08 13:26:54 |
| Message-ID: | CAFj8pRDq2LTHmpcw8XipATjBE1NPbBSvxSJ4=uqNAR=kjY5_8Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi
2016-07-08 15:16 GMT+02:00 <AMatveev(at)bitec(dot)ru>:
> Hi
>
> > On 08/07/2016 14:11, AMatveev(at)bitec(dot)ru wrote:
> >> Hi.
> >> The test performs about 11K lines of code
> >> Memory usage per session:
> >> Oracle: about 5M
> >> MSSqlServer: about 4M
> >> postgreSql: about 160М
>
>
> > Visual C???
> > You will have to run PostgreSQL on a proper Unix system to test for
> performance.
> Of cause we understand that unix is faster( damn fork :)))
> Our Current problem is memory:
> (160m vs 5M) * 100 sessions = 16G vs 0.5G
> We just can get "out of memory".
> :(((
>
The almost session memory is used for catalog caches. So you should to have
big catalog and long living sessions.
What do you do exactly?
Regards
Pavel
>
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John McKown | 2016-07-08 13:27:00 | Re: Memory usage per session |
| Previous Message | AMatveev | 2016-07-08 13:16:23 | Re: Memory usage per session |