JESS: performance trade-of in updateObject(...)

[Florian Fischer]

Hello,

I was wondering what is the performance trade-off between
   rete.updateObject(myObject);
and
   rete.updateObject(myObject, slot);
When I update an object underlying a shadow fact, I record the list of 
updated fields and call updateObject only at the end.  If only one field 
was updated I pass the slot name as parameter.  If I updated more than 
one, I make a global update.

But for instance, when updating 2 fields out of 91, would it make sense 
to do two specific updateObject, one for each slot, instead of one 
global update?  If I do a global updateObject, it will have to reread 
all 91 fields.  If I do two specific updateObject, it might reorganize 
the Rete network twice.  So which is better?

Would it make sense to implement a updateObject(String[] slots) for the 
case where you know which fields were updated?

Thanks in advance,
Florian Fischer

--
Florian Fischer
Service d'Informatique Médicale
Hôpitaux Universitaires de Genève
Tél: 022 37 28861
[EMAIL PROTECTED]



--------------------------------------------------------------------
To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]'
in the BODY of a message to [EMAIL PROTECTED], NOT to the list
(use your own address!) List problems? Notify [EMAIL PROTECTED]
--------------------------------------------------------------------