ObjectSynchronizer iterate only in-use monitors?
Thomas Schatzl
thomas.schatzl at oracle.com
Tue May 16 08:05:24 UTC 2017
Hi,
On Tue, 2017-05-16 at 09:58 +0200, Roman Kennke wrote:
> Am 16.05.2017 um 09:54 schrieb Thomas Schatzl:
> > On Tue, 2017-05-16 at 09:43 +0200, Roman Kennke wrote:
> > > E.g.:
> > >
> > > http://cr.openjdk.java.net/~rkennke/deflate-per-thread/webrev.01/
> > >
> > > I can probably collapse monitor deflation and iteration into one
> > > pass too.
> >
> > is there a problem to just activate this by default and avoid
> > adding an (experimental) option? Even experimental options are part
> > of the public API (as they can be accessed in the product) and need
> > a CSR request to add and need to go through the usual long-winded
> > procedure to remove later (after we find out after 10 years that
> > nobody ever actually uses that one).
> >
> > I mean, this change seems to be a win in all cases (or at most be
> > as slow as before), so why allow the user to mess with it?
> There's no problem. I made it this way mostly for me to be able to
> test and compare side-by-side easily :-) Will post RFR without the
> flag after I've done some more testing...
Okay, thanks a lot :D
Thanks,
Thomas
More information about the hotspot-runtime-dev
mailing list