Sanne Grinovero [
http://community.jboss.org/people/sannegrinovero] created the discussion
"Re: dynamic reconfiguration"
To view the discussion, visit:
http://community.jboss.org/message/633534#633534
--------------------------------------------------------------
While profiling HibernateOGM, the bottlenecks are currently in other projects code but
while they are being solved the impact of these Map lookups in the transaction manager are
getting more significant every day - currently consuming around 2% of total CPU time,
I'd expect this ratio to grow soon as we solve other issues, so it would be nice to
avoid the lookups as much as possible. Fixing
https://issues.jboss.org/browse/JBTM-929
JBTM-929 was a good improvement.
About the eventbus, that seems interesting but the changed properties would need to set a
memory barrier whose cost is paid for at each read, for example a volatile might become
costly on non-x86 CPUs - is that something we should be concerned about?
Hibernate 4 introduced an internal ConcurrentHashMap "ServiceRegistry" holding
all the main components; this provides more flexibility but is introducing a new runtime
cost: not significant when connecting to a slow JDBC database, more concerning when
connecting to a data grid: often we have to cache references to components, losing the
option to hot-swap them.
Delaying the freeze point sounds nice to me, but I'm unfit to judge about the
Transactions implementation internals. I've often used lazy static initialization to
temporarily workaround performance problems, but it's hard to maintain and I've
never suggested introducing it in a mission critical library.
--------------------------------------------------------------
Reply to this message by going to Community
[
http://community.jboss.org/message/633534#633534]
Start a new discussion in JBoss Transactions Development at Community
[
http://community.jboss.org/choose-container!input.jspa?contentType=1&...]