Re: JESS: [EXTERNAL] Jess in a multithreaded environment

--_000_7F2CAF6713AFDD4392FC4DAA05671E072C4CFEA4EXMB10srnsandia_
Content-Type: text/plain;
 charset=us-ascii
Content-Transfer-Encoding: quoted-printable

Are you adding non-value classes to the list yourself, or is this just with=
 the small number of default listings?

This method will get called when you evaluate the hash code of a Java objec=
t in the Rete memory; this will happen often during pattern matching. There=
's actually enough room to cache the hash code in the members of the Value =
class that are unused for Java object values, so we could try that as a per=
formance improvement.  Do you have a source license, so I could send you a =
patch to try?

From: <Nguyen>, Son Nguyen <[email protected]<mailto:Son.Nguyen@sof=
twareag.com>>
Reply-To: jess-users <[email protected]<mailto:jess-users@mail=
gate.sandia.gov>>
Date: Thursday, December 13, 2012 11:04 AM
To: jess-users <[email protected]<mailto:[email protected]=
andia.gov>>
Subject: JESS: [EXTERNAL] Jess in a multithreaded environment



Hi Jess experts,

We use Jess in a multi-threaded environment and have experienced some perfo=
rmance degradation when going from a single thread to multiple threads.

Our implementation uses the Slot Specific feature.

Using a Java profiler, HashCodeComputer.isValueObject() stood out as one of=
 the main contributing factors, if not the most likely,  to the degradation=
--_000_7F2CAF6713AFDD4392FC4DAA05671E072C4CFEA4EXMB10srnsandia_--