[Hibernate-JIRA] Created: (HHH-7190) [Performance] - Degradation hibernate time after migration hibernate 3.3.1.GA --> 4.0.1
9:13 a.m.
[Performance] - Degradation hibernate time after migration hibernate 3.3.1.GA -->
4.0.1
---------------------------------------------------------------------------------------
Key: HHH-7190
URL: https://hibernate.onjira.com/browse/HHH-7190
Project: Hibernate ORM
Issue Type: Bug
Components: core
Affects Versions: 4.1.1, 4.0.1
Environment: java version "1.6.0_23"
Java(TM) SE Runtime Environment (build 1.6.0_23-b05)
Java HotSpot(TM) 64-Bit Server VM (build 19.0-b09, mixed mode)
Reporter: Lucas POUZAC
Priority: Blocker
Attachments: hibernate.jpg
After migrating our application to version 4.0.1 of hibernate, we noticed a performance
degradation. (same problem with the version 4.1.1)
Before migration, the average response time of our http request was 747ms (during load
test).
Since the migration, the average response time is greater than 1200ms (during the same
load test).
After recording the behavior of the JVM, we note that Hibernate uses methods of the java
api with synchronized blocks (java.lang.reflect.Proxy.getProxyClass (...)). See
attachment.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:49 p.m.
New subject: [Hibernate-JIRA] Updated: (HHH-7190) [Performance] - Degradation hibernate time after migration hibernate 3.3.1.GA --> 4.0.1
[
https://hibernate.onjira.com/browse/HHH-7190?page=com.atlassian.jira.plug...
]
Steve Ebersole updated HHH-7190:
--------------------------------
Priority: Major (was: Blocker)
Labels: performance (was: )
First, I cannot see the details in this attached image. It is way too small using any
tools I have here to make anything out.
Second, Hibernate 4 has been perf tested against both 3.3 and 3.6 quite a few different
times and each time has shown faster than 3.3/3.6.
[Performance] - Degradation hibernate time after migration hibernate
3.3.1.GA --> 4.0.1
---------------------------------------------------------------------------------------
Key: HHH-7190
URL: https://hibernate.onjira.com/browse/HHH-7190
Project: Hibernate ORM
Issue Type: Bug
Components: core
Affects Versions: 4.0.1, 4.1.1
Environment: java version "1.6.0_23"
Java(TM) SE Runtime Environment (build 1.6.0_23-b05)
Java HotSpot(TM) 64-Bit Server VM (build 19.0-b09, mixed mode)
Reporter: Lucas POUZAC
Labels: performance
Attachments: hibernate.jpg
After migrating our application to version 4.0.1 of hibernate, we noticed a performance
degradation. (same problem with the version 4.1.1)
Before migration, the average response time of our http request was 747ms (during load
test).
Since the migration, the average response time is greater than 1200ms (during the same
load test).
After recording the behavior of the JVM, we note that Hibernate uses methods of the java
api with synchronized blocks (java.lang.reflect.Proxy.getProxyClass (...)). See
attachment.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:29 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-7190) [Performance] - Degradation hibernate time after migration hibernate 3.3.1.GA --> 4.0.1
[
https://hibernate.onjira.com/browse/HHH-7190?page=com.atlassian.jira.plug...
]
Lucas POUZAC commented on HHH-7190:
-----------------------------------
You could zoom this attached file if you load in new browser tab.
Regards
[Performance] - Degradation hibernate time after migration hibernate
3.3.1.GA --> 4.0.1
---------------------------------------------------------------------------------------
Key: HHH-7190
URL: https://hibernate.onjira.com/browse/HHH-7190
Project: Hibernate ORM
Issue Type: Bug
Components: core
Affects Versions: 4.0.1, 4.1.1
Environment: java version "1.6.0_23"
Java(TM) SE Runtime Environment (build 1.6.0_23-b05)
Java HotSpot(TM) 64-Bit Server VM (build 19.0-b09, mixed mode)
Reporter: Lucas POUZAC
Labels: performance
Attachments: hibernate.jpg
After migrating our application to version 4.0.1 of hibernate, we noticed a performance
degradation. (same problem with the version 4.1.1)
Before migration, the average response time of our http request was 747ms (during load
test).
Since the migration, the average response time is greater than 1200ms (during the same
load test).
After recording the behavior of the JVM, we note that Hibernate uses methods of the java
api with synchronized blocks (java.lang.reflect.Proxy.getProxyClass (...)). See
attachment.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:15 a.m.
New subject: [Hibernate-JIRA] Updated: (HHH-7190) Cache JDBC proxy class defintions
[
https://hibernate.onjira.com/browse/HHH-7190?page=com.atlassian.jira.plug...
]
Steve Ebersole updated HHH-7190:
--------------------------------
Summary: Cache JDBC proxy class defintions (was: [Performance] - Degradation
hibernate time after migration hibernate 3.3.1.GA --> 4.0.1)
Cache JDBC proxy class defintions
---------------------------------
Key: HHH-7190
URL: https://hibernate.onjira.com/browse/HHH-7190
Project: Hibernate ORM
Issue Type: Improvement
Components: core
Affects Versions: 4.0.1, 4.1.1
Environment: java version "1.6.0_23"
Java(TM) SE Runtime Environment (build 1.6.0_23-b05)
Java HotSpot(TM) 64-Bit Server VM (build 19.0-b09, mixed mode)
Reporter: Lucas POUZAC
Labels: performance
Attachments: hibernate.jpg
After migrating our application to version 4.0.1 of hibernate, we noticed a performance
degradation. (same problem with the version 4.1.1)
Before migration, the average response time of our http request was 747ms (during load
test).
Since the migration, the average response time is greater than 1200ms (during the same
load test).
After recording the behavior of the JVM, we note that Hibernate uses methods of the java
api with synchronized blocks (java.lang.reflect.Proxy.getProxyClass (...)). See
attachment.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:15 a.m.
New subject: [Hibernate-JIRA] Updated: (HHH-7190) [Performance] - Degradation hibernate time after migration hibernate 3.3.1.GA --> 4.0.1
[
https://hibernate.onjira.com/browse/HHH-7190?page=com.atlassian.jira.plug...
]
Steve Ebersole updated HHH-7190:
--------------------------------
Issue Type: Improvement (was: Bug)
[Performance] - Degradation hibernate time after migration hibernate
3.3.1.GA --> 4.0.1
---------------------------------------------------------------------------------------
Key: HHH-7190
URL: https://hibernate.onjira.com/browse/HHH-7190
Project: Hibernate ORM
Issue Type: Improvement
Components: core
Affects Versions: 4.0.1, 4.1.1
Environment: java version "1.6.0_23"
Java(TM) SE Runtime Environment (build 1.6.0_23-b05)
Java HotSpot(TM) 64-Bit Server VM (build 19.0-b09, mixed mode)
Reporter: Lucas POUZAC
Labels: performance
Attachments: hibernate.jpg
After migrating our application to version 4.0.1 of hibernate, we noticed a performance
degradation. (same problem with the version 4.1.1)
Before migration, the average response time of our http request was 747ms (during load
test).
Since the migration, the average response time is greater than 1200ms (during the same
load test).
After recording the behavior of the JVM, we note that Hibernate uses methods of the java
api with synchronized blocks (java.lang.reflect.Proxy.getProxyClass (...)). See
attachment.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:19 a.m.
New subject: [Hibernate-JIRA] Updated: (HHH-7190) Cache JDBC proxy class defintions
[
https://hibernate.onjira.com/browse/HHH-7190?page=com.atlassian.jira.plug...
]
Steve Ebersole updated HHH-7190:
--------------------------------
Assignee: Steve Ebersole
Cache JDBC proxy class defintions
---------------------------------
Key: HHH-7190
URL: https://hibernate.onjira.com/browse/HHH-7190
Project: Hibernate ORM
Issue Type: Improvement
Components: core
Affects Versions: 4.0.1, 4.1.1
Environment: java version "1.6.0_23"
Java(TM) SE Runtime Environment (build 1.6.0_23-b05)
Java HotSpot(TM) 64-Bit Server VM (build 19.0-b09, mixed mode)
Reporter: Lucas POUZAC
Assignee: Steve Ebersole
Labels: performance
Attachments: hibernate.jpg
After migrating our application to version 4.0.1 of hibernate, we noticed a performance
degradation. (same problem with the version 4.1.1)
Before migration, the average response time of our http request was 747ms (during load
test).
Since the migration, the average response time is greater than 1200ms (during the same
load test).
After recording the behavior of the JVM, we note that Hibernate uses methods of the java
api with synchronized blocks (java.lang.reflect.Proxy.getProxyClass (...)). See
attachment.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:19 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-7190) Cache JDBC proxy class defintions
[
https://hibernate.onjira.com/browse/HHH-7190?page=com.atlassian.jira.plug...
]
Steve Ebersole commented on HHH-7190:
-------------------------------------
Current code is using {{java.lang.reflect.Proxy#newProxyInstance}}, which is a convenience
method. However, this does require calls into the synchronized method
{{java.lang.reflect.Proxy#getProxyClass}} each and every time a proxy instance is
generated. In concurrent systems that sync is a potential bottleneck.
Switching to explicitly building and holding on to the proxy class reference and then
manually instantiating the proxies as needed through that class reference, rather than
using the convenience method, should eliminate that bottleneck.
Cache JDBC proxy class defintions
---------------------------------
Key: HHH-7190
URL: https://hibernate.onjira.com/browse/HHH-7190
Project: Hibernate ORM
Issue Type: Improvement
Components: core
Affects Versions: 4.0.1, 4.1.1
Environment: java version "1.6.0_23"
Java(TM) SE Runtime Environment (build 1.6.0_23-b05)
Java HotSpot(TM) 64-Bit Server VM (build 19.0-b09, mixed mode)
Reporter: Lucas POUZAC
Labels: performance
Attachments: hibernate.jpg
After migrating our application to version 4.0.1 of hibernate, we noticed a performance
degradation. (same problem with the version 4.1.1)
Before migration, the average response time of our http request was 747ms (during load
test).
Since the migration, the average response time is greater than 1200ms (during the same
load test).
After recording the behavior of the JVM, we note that Hibernate uses methods of the java
api with synchronized blocks (java.lang.reflect.Proxy.getProxyClass (...)). See
attachment.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:06 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-7190) Cache JDBC proxy class defintions
[
https://hibernate.onjira.com/browse/HHH-7190?page=com.atlassian.jira.plug...
]
Steve Ebersole commented on HHH-7190:
-------------------------------------
See if that helps. 4.1.2 is just over 2 weeks away, so if you can verify before then we
can work to get any other adjustments in...
Cache JDBC proxy class defintions
---------------------------------
Key: HHH-7190
URL: https://hibernate.onjira.com/browse/HHH-7190
Project: Hibernate ORM
Issue Type: Improvement
Components: core
Affects Versions: 4.0.1, 4.1.1
Environment: java version "1.6.0_23"
Java(TM) SE Runtime Environment (build 1.6.0_23-b05)
Java HotSpot(TM) 64-Bit Server VM (build 19.0-b09, mixed mode)
Reporter: Lucas POUZAC
Assignee: Steve Ebersole
Labels: performance
Fix For: 4.1.2
Attachments: hibernate.jpg
Time Spent: 44m
After migrating our application to version 4.0.1 of hibernate, we noticed a performance
degradation. (same problem with the version 4.1.1)
Before migration, the average response time of our http request was 747ms (during load
test).
Since the migration, the average response time is greater than 1200ms (during the same
load test).
After recording the behavior of the JVM, we note that Hibernate uses methods of the java
api with synchronized blocks (java.lang.reflect.Proxy.getProxyClass (...)). See
attachment.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:06 a.m.
New subject: [Hibernate-JIRA] Resolved: (HHH-7190) Cache JDBC proxy class defintions
[
https://hibernate.onjira.com/browse/HHH-7190?page=com.atlassian.jira.plug...
]
Steve Ebersole resolved HHH-7190.
---------------------------------
Resolution: Fixed
Fix Version/s: 4.1.2
Cache JDBC proxy class defintions
---------------------------------
Key: HHH-7190
URL: https://hibernate.onjira.com/browse/HHH-7190
Project: Hibernate ORM
Issue Type: Improvement
Components: core
Affects Versions: 4.0.1, 4.1.1
Environment: java version "1.6.0_23"
Java(TM) SE Runtime Environment (build 1.6.0_23-b05)
Java HotSpot(TM) 64-Bit Server VM (build 19.0-b09, mixed mode)
Reporter: Lucas POUZAC
Assignee: Steve Ebersole
Labels: performance
Fix For: 4.1.2
Attachments: hibernate.jpg
Time Spent: 44m
After migrating our application to version 4.0.1 of hibernate, we noticed a performance
degradation. (same problem with the version 4.1.1)
Before migration, the average response time of our http request was 747ms (during load
test).
Since the migration, the average response time is greater than 1200ms (during the same
load test).
After recording the behavior of the JVM, we note that Hibernate uses methods of the java
api with synchronized blocks (java.lang.reflect.Proxy.getProxyClass (...)). See
attachment.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4664
days inactive
4666
days old
hibernate-issues@lists.jboss.org
8 comments
2 participants
participants (2)
-
Lucas POUZAC (JIRA) -
Steve Ebersole (JIRA)