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

>heap dump analysed with MAT

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.