8010309 : PlatformLogger: isLoggable performance / waste due to HashMap<Integer, Level (original) (raw)
Peter Levart peter.levart at gmail.com
Wed Mar 27 10:19:51 UTC 2013
- Previous message: 8010309 : PlatformLogger: isLoggable performance / waste due to HashMap<Integer, Level> leads to Integer allocations (boxing)
- Next message: 8010309 : PlatformLogger: isLoggable performance / waste due to HashMap<Integer, Level> leads to Integer allocations (boxing)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 03/27/2013 10:32 AM, Laurent Bourgès wrote:
Hi Mandy, Peter,
thanks for the review. I wanted the patch to be small and only in PlatformLogger class without API change to be easily backported to jdk7u. Do you think this bug is JDK8 only ?
I think this API level change is source-level-compatible, so only a JDK rebuild is required. Will try it anyway and check whether this is true. If it is then the backport is not a problem.
Regards, Peter
http://bugs.sun.com/bugdatabase/viewbug.do?bugid=8010309 I submitted another patch concerning missing PlatformLogger.isLoggable(level) in the JDK (java.net <http://java.net>, java.awt mainly) but it is not widely used as I thought first. see http://mail.openjdk.java.net/pipermail/awt-dev/2013-March/004459.html Maybe in the future, other projects or JDK parts will use it if it is no more a performance bottleneck. Cheers, Laurent
- Previous message: 8010309 : PlatformLogger: isLoggable performance / waste due to HashMap<Integer, Level> leads to Integer allocations (boxing)
- Next message: 8010309 : PlatformLogger: isLoggable performance / waste due to HashMap<Integer, Level> leads to Integer allocations (boxing)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]