On Fri, Jul 8, 2016 at 11:49 AM, <amatv...@bitec.ru> 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 instruction tree size for our > production code. > This test shows: > -What is the size of instruction tree for our typical BP > it's greater than 300M for each session > -How often do PostgreSql parse the text > When postgres clean cache, so much often > > So Oracle is much better in this case. > It's very difficult really estimate in such case, to buy Oracle or to by > hardware. > >
*My questions:*>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 have specified in postgresql.conf? > Also, what is the exact version of PostgreSQL you are using? >What is the total time to complete the test for all 3 DB's? >The best I can tell is that with all the unknowns, you are comparing apples to oranges. *Your answers:* >There is real problem for us. >The PL/pgSQL interpreter parses the function's source text and produces an internal binary instruction tree the first time the function is called (within each session) *Your answer is jibberish and has nothing to do with my questions.* *Have you even tuned the postgresql.conf?* *You cannot fairly compare PostgreSQL with any other database unless you first tune it's postgres.conf.* *Melvin Davidson* I reserve the right to fantasize. Whether or not you wish to share my fantasy is entirely up to you.
