| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | AMatveev(at)bitec(dot)ru |
| Cc: | Achilleas Mantzios <achill(at)matrix(dot)gatewaynet(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Memory usage per session |
| Date: | 2016-07-08 13:35:50 |
| Message-ID: | 20160708133549.GI21416@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
* AMatveev(at)bitec(dot)ru (AMatveev(at)bitec(dot)ru) wrote:
> > On 08/07/2016 14:11, AMatveev(at)bitec(dot)ru wrote:
> >> 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".
> :(((
Do you have 100 CPUs on this system which apparently doesn't have 16G
of RAM available for PG to use?
If not, you should probably consider connection pooling to reduce the
number of PG sessions to something approaching the number of CPUs/cores
you have in the system.
Thanks!
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | AMatveev | 2016-07-08 14:07:00 | Re: Memory usage per session |
| Previous Message | John McKown | 2016-07-08 13:27:00 | Re: Memory usage per session |