Details
-
Task
-
Status: Closed
-
Major
-
Resolution: Abandoned
-
1.3.0
-
None
-
None
Description
I think there's room for improvement in our client's memory profile. I ran ltt with jfr running, attaching some snaps of what my client sees. Looks like some kind of object pool or block encoding for result objects will give us a lot of bang for the buck re: allocations and GC pressure. We probably also want to look for an alternative way to represent result objects, something besides the java Map interface with it's Entry bloat.