From: | AMatveev(at)bitec(dot)ru |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net> |
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 14:07:00 |
Message-ID: | 1433692435.20160708170700@bitec.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi
>> >> The test performs about 11K lines of code
>> >> Oracle: about 5M
>> >> postgreSql: about 160М
> Do you have 100 CPUs on this system which apparently doesn't have 16G
> of RAM available for PG to use?
We can say at fact:
We currently work at oracle.
Our code base about 4000 k line of code
In out last project we have:
3000 current connection
200 active session
So 16g it's very optimistic.
Of course we think about buy hardware or software.
It's other question.
So with this memory consumption it can be really cheaper to by Oracle.
> 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.
It's possible only with application server,
for local network thick client has reasonable advantages.
We just can't implement today all functions on thin client.
From | Date | Subject | |
---|---|---|---|
Next Message | AMatveev | 2016-07-08 14:29:54 | Re: Memory usage per session |
Previous Message | Stephen Frost | 2016-07-08 13:35:50 | Re: Memory usage per session |