On Sun, Nov 25, 2018 at 3:19 AM Oleg Kalnichevski <[email protected]> wrote:
> On Sat, 2018-11-24 at 21:43 -0800, Ryan Schmitt wrote: > > Where's the grief, exactly? The fact that these objects are showing > > up > > in heap dumps does not imply performance impact, and no performance > > impact was claimed, nor were any measurements provided. To state that > > iterators "have to be garbage collected" is misleading; the Java > > garbage collector traces live objects, never looking at garbage, > > which > > means that ephemeral garbage is virtually free. > > Please quantify being 'virtually free' and provide measurements to > support the claim. > Oh boy, it feels like all sides are claiming some performance characteristics and in each case the other side is asking for evidence... :-( Gary > > Oleg > > > > You also have to > > consider JVM optimizations like scalar replacement, which is > > basically > > an approximation of stack allocation. Gary also makes a good point > > about how replacing iteration with index access on a List can > > backfire > > depending on the underlying implementation of List. > > > > On Fri, Nov 23, 2018 at 12:20 AM Oleg Kalnichevski <[email protected]> > > wrote: > > > > > > I am _strongly_ against it. Last time you did that it had caused us > > > a > > > lot of grief. > > > > > > https://issues.apache.org/jira/browse/HTTPCORE-361 > > > > > > Oleg > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
