[
https://issues.apache.org/jira/browse/ZOOKEEPER-1232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Koch updated ZOOKEEPER-1232:
-----------------------------------
Attachment: ZOOKEEPER-1232.patch
> remove unused o.a.z.server.util.Profiler
> ----------------------------------------
>
> Key: ZOOKEEPER-1232
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1232
> Project: ZooKeeper
> Issue Type: Bug
> Reporter: Thomas Koch
> Assignee: Thomas Koch
> Attachments: ZOOKEEPER-1232.patch
>
>
> The class is not used and it rather harms to suggest to people that this
> would be the right way to do micro-benchmarks on the JVM. It even harms to
> suggest that micro-benchmarks are the right way to approach Java performance
> issues.
> Quote from http://code.google.com/p/caliper/wiki/JavaMicrobenchmarks
> "Why would I ever write a microbenchmark then?
> Most of the time, you shouldn't! Instead, slavishly follow a principle of
> simple, clear coding that avoids clever optimizations. This is the type of
> code that JITs of the present and future are most likely to know how to
> optimize themselves. And that's a job which truly should be theirs, not
> yours. "
> Tools to do microbenchmarks:
> http://code.google.com/p/caliper/ (from the team that also does Guava, the
> Google Java library, recommended by Joshua Bloch himself)
> http://hype-free.blogspot.com/2010/01/choosing-java-profiler.html
> http://www.infoq.com/articles/java-profiling-with-open-source
> http://java.net/projects/japex
> Joshua Bloch on Performance Anxiety:
> http://java.dzone.com/articles/joshua-bloch-performance (follow link to
> parleys)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
