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
On 7/8/2016 12:00 PM, Karl Czajkowski wrote:
3. Rewrite or refactor such complex stored procedures in a different
programming language such as C or Python, so your PL/pgsql stored
procedures remain small glue around libraries of code. Postgres
makes it very trivial to extend the syst
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. This parse tre
2016-07-08 17:49 GMT+02:00 :
> 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 t
On Fri, Jul 8, 2016 at 11:26 AM, Melvin Davidson
wrote:
>
>
> On Fri, Jul 8, 2016 at 11:49 AM, wrote:
>
>> 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
On Fri, Jul 8, 2016 at 11:49 AM, wrote:
> 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 i
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 tha
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?
On 08/07/2016 17:07, amatv...@bitec.ru wrote:
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
On Fri, Jul 8, 2016 at 10:07 AM, wrote:
> 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 cur
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
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
* amatv...@bitec.ru (amatv...@bitec.ru) wrote:
> > On 08/07/2016 14:11, amatv...@bitec.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 Pos
On Fri, Jul 8, 2016 at 8:16 AM, wrote:
> 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
Hi
2016-07-08 15:16 GMT+02:00 :
> 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
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
On 08/07/2016 14:11, amatv...@bitec.ru wrote:
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 abo
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
19 matches
Mail list logo
