Hi
>I think the "problem" that he is having is fixable only by changing how
>PostgreSQL itself works.
>His problem is a PL/pgSQL function which is 11K lines in length.
>When invoked, this function is "compiled" into a large tokenized parse tree.
>This parse tree is only usable in the session whic
Hi
> On Jul 08, John McKown modulated:
> ...
>> I think the "problem" that he is having is fixable only by changing how
>> PostgreSQL itself works. His problem is a PL/pgSQL function which is
>> 11K lines in length. When invoked, this function is "compiled" into a
>> large tokenized parse tree. Th
Title: Re: [GENERAL] Memory usage per session
Hi
>> Oracle: about 5M
>> postgreSql: about 160М
>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?
I've generate test code that emulates instruction tre
Title: Re: [GENERAL] Memory usage per session
Hi
>> >> The test performs about 11K lines of code
>> >> Oracle: about 5M
>> >> postgreSql: about 160М
>What is the actual O/S that PostgreSQL is installed on?
>How much total memory is on the server?
>I would be very curious about the values you
Title: Re: [GENERAL] Memory usage per session
Здравствуйте.
>> Oracle: about 5M
>> postgreSql: about 160М
>I'm admittedly ignorant of this type of testing. But if the memory usage for PostgreSQL is in the server, perhaps due to caching (how to test?), then it likely would _not_ linearly scale
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 co
Hi
> On 08/07/2016 14:11, amatv...@bitec.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
> perfor
Hi.
We have tested postgreSql,Oracle,MSSqlServer.
The test performs about 11K lines of code
Memory usage per session:
Oracle: about 5M
MSSqlServer: about 4M
postgreSql: about 160М
The result of postgreSql is very sad(Our typical business logic has about 30K
lines of code).
How can I reduce memory