[
https://issues.jboss.org/browse/JASSIST-163?page=com.atlassian.jira.plugi...
]
Nikita Tovstoles updated JASSIST-163:
-------------------------------------
Attachment: Product_$$_javassist_0.java
I decompiled output of ProxyFactory.createClass(). Here's what makeForwarder does for
each proxied method (full decompiled src attached):
{code}
//target pojo has a getName() method
public final String getName()
{
Method[] arrayOfMethod = _methods_;
RuntimeSupport.find2Methods(this, "getName", "_d7getName", 14,
"()Ljava/lang/String;", arrayOfMethod);
return (String)this.handler.invoke(this, arrayOfMethod[14], arrayOfMethod[15], new
Object[0]);
}
{code}
..looks like static Method[] methods is lazily filled, perhaps as a perf/memory
optimization. Clearly repeat calls to find2Methods need to be avoided.
Not yet clear if, instead of caching, it'd make more sense to fill _methods_ eagerly
during during proxy class creation and avoid any calls to find2methods during calls
against proxy instance
RuntimeSupport.find2Methods a perf hotspot when proxy's methods
are called at higher concurrency
------------------------------------------------------------------------------------------------
Key: JASSIST-163
URL:
https://issues.jboss.org/browse/JASSIST-163
Project: Javassist
Issue Type: Enhancement
Affects Versions: 3.15.0-GA, 3.16.1-GA
Environment: hibernate-core 3.6.10.Final
Reporter: Nikita Tovstoles
Assignee: Shigeru Chiba
Attachments: blocked-threads.png, find2methods-hotspot.png,
monitor-backtraces.png, monitor-backtraces.png, Product_$$_javassist_0.java,
Tomcat-2012-03-28(2).zip
We've been profiling our Hibernate 3.6.10-based app and noticed a perf bottleneck in
javassist.util.proxy.RuntimeSupport.find2methods. Unfortunately, this method, which has a
synch. block, is being called on
every invocation of every proxied entity method (see
javassist.util.proxy.ProxyFactory.makeForwarder(), called indirectly by
ProxyFactory.createClass()).
In our testing, the result is that our service call's latency increases from 33 to
55, 260, 400ms as concurrency increases
1-10-20-30 users on a 4-core CPU. At 20 and 30 users 51% of CPU time is spent contending
for a monitor in RuntimeSupport.find2methods:
{code}
synchronized (methods) {
if (methods[index] == null) {
methods[index + 1] = thisMethod == null ? null
: findMethod(self, thisMethod, desc);
methods[index] = findSuperMethod(self, superMethod, desc);
}
}
{code}
Since find2methods merely interrogates class metadata, seems like its return values
should be cached (in a ConcurrentMap?) instead of repeatedly executing the above
synchronized statement. Instead, currently, it's being called every time (?) a proxied
method is executed - see *Invocation Count* in this screen shot:
https://issues.jboss.org/secure/attachment/12353025/monitor-backtraces.png
Full [YourKit
profile|http://yourkit.com] is [attached as a ZIP
archive|^Tomcat-2012-03-28(2).zip]; key screen shots from the snapshot also attached
separately
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira