Re: java.lang.OutOfMemoryError: GC overhead limit exceeded - Mailing list pgsql-jdbc

From Vladimir Sitnikov
Subject Re: java.lang.OutOfMemoryError: GC overhead limit exceeded
Date
Msg-id CAB=Je-HjCjHxkCY3WW_WLy0XGwXqs_r5Db4daWLrdbYpT21wvA@mail.gmail.com
Whole thread Raw
In response to Re: java.lang.OutOfMemoryError: GC overhead limit exceeded  (Christophe combet <chrisc_pro@yahoo.fr>)
List pgsql-jdbc
>heap dump analysed with MAT

Thank you.

Even though the preferred solution is to buffer data rather than fetch all the rows to the heap, it looks like Tuple costs 30% or so of the heap :-/
Just in case, the columns are "number of objects", "shallow heap" (==heap consumption by the object itself), "retained heap" (==heap consumption of the object+all its references).
We might want to revise the addition of Tuple.

Vladimir

pgsql-jdbc by date:

Previous
From: Thomas Kellerer
Date:
Subject: Re: java.lang.OutOfMemoryError: GC overhead limit exceeded
Next
From: Vladimir Sitnikov
Date:
Subject: [pgjdbc/pgjdbc] 671558: chore: add S3 Gradle build cache