commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From henrib <>
Subject Re: JEXL3 Performance degradation compared to 2.1.1
Date Fri, 22 Jan 2016 19:19:28 GMT
Since performance is the same with the workaround, we've got
another/different performance issue. Is there any easy way to replicate your
test - or at least its essence - ? What does your benchmark do ? What are
the evaluated expressions / scripts ?

Back too your note: the 'size' method is discovered through introspection as
an overload of the 'size' operator; this creates an entry in a cache for
that arithmetic class avoiding to re-discover the operator overloads
(Uberspect) on each execution. So, no, this method is not called; it is just
meant as a workaround of the bug.


View this message in context:
Sent from the Commons - User mailing list archive at

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message