Re: java.lang.OutOfMemoryError: GC overhead limit exceeded

From: Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com>
To: Christophe combet <chrisc_pro(at)yahoo(dot)fr>
Cc: pgsql-jdbc(at)lists(dot)postgresql(dot)org
Subject: Re: java.lang.OutOfMemoryError: GC overhead limit exceeded
Date: 2020-07-23 18:03:45
Message-ID: CAB=Je-HjCjHxkCY3WW_WLy0XGwXqs_r5Db4daWLrdbYpT21wvA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-jdbc by date

  From Date Subject
Next Message Vladimir Sitnikov 2020-07-25 11:16:58 [pgjdbc/pgjdbc] 671558: chore: add S3 Gradle build cache
Previous Message Thomas Kellerer 2020-07-23 17:32:48 Re: java.lang.OutOfMemoryError: GC overhead limit exceeded