Re: Reducing Garbage Generated by URLClassLoader

2016-12-05 Thread Scott Palmer
> On Dec 5, 2016, at 1:31 AM, Max Kanat-Alexander wrote: > > Yeah, I have implemented a fast-path byte-only ZipCoder in a customized JDK > and it makes a big difference for allocations in long classpaths. I expected to see an improvement, but haven’t made any attempt at solving the problem yet

Re: Reducing Garbage Generated by URLClassLoader

2016-12-04 Thread Xueming Shen
On 12/4/16, 1:21 PM, Scott Palmer wrote: Excuse me if this is the wrong list for this discussion. Please direct me to the right place if this isn’t it. When doing an analysis of garbage generation in our application we discovered a significant number of redundant strings generated by the clas

Re: Reducing Garbage Generated by URLClassLoader

2016-12-04 Thread Claes Redestad
Hi Scott, On 12/04/2016 01:21 PM, Scott Palmer wrote: Excuse me if this is the wrong list for this discussion. Please direct me to the right place if this isn’t it. I think this is a good place based on the aspects you're addressing. When doing an analysis of garbage generation in our app

Reducing Garbage Generated by URLClassLoader

2016-12-04 Thread Scott Palmer
Excuse me if this is the wrong list for this discussion. Please direct me to the right place if this isn’t it. When doing an analysis of garbage generation in our application we discovered a significant number of redundant strings generated by the class loader. In my case there are hundreds o