]
Mark Proctor commented on DROOLS-485:
-------------------------------------
We have done significant work around thread safety:
Not sure if all our contention points are fixed though, although we have improved this.
Can you try latest 7.x snapshot and confirm?
@tzimanyi [~mfusco] ^ are we able to confirm this on our side? Do we have this in a
regression benchmark?
Drools 6 large contention
-------------------------
Key: DROOLS-485
URL:
https://issues.jboss.org/browse/DROOLS-485
Project: Drools
Issue Type: Bug
Affects Versions: 6.0.0.Final
Environment: JDK6, 4 physical CPU cores
Reporter: Sergey Alaev
Assignee: Mark Proctor
Rules run almost sequentially, i.e. running in two threads results in doubling execution
time.
Profiler shows following contention points:
Stack Trace Count Duration
org.drools.core.phreak.SegmentUtilities.createSegmentMemory(LeftTupleSource,
InternalWorkingMemory) 3,301 270,505,102,344
org.drools.core.phreak.SegmentUtilities.createChildSegments(InternalWorkingMemory,
SegmentMemory, LeftTupleSinkPropagator) 2,997 232,087,570,565
org.drools.core.runtime.process.ProcessRuntimeFactory.getProcessRuntimeFactoryService() 121 2,922,590,350