You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Henri Biestro (Jira)" <ji...@apache.org> on 2021/06/29 07:00:03 UTC
[jira] [Closed] (JEXL-186) Performance regression in arithmetic
operations compared to JEXL 2.1
[ https://issues.apache.org/jira/browse/JEXL-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Henri Biestro closed JEXL-186.
------------------------------
> Performance regression in arithmetic operations compared to JEXL 2.1
> --------------------------------------------------------------------
>
> Key: JEXL-186
> URL: https://issues.apache.org/jira/browse/JEXL-186
> Project: Commons JEXL
> Issue Type: Bug
> Affects Versions: 3.0
> Reporter: Philippe Mouawad
> Assignee: Henri Biestro
> Priority: Major
> Fix For: 3.1
>
> Attachments: PerfJexl2.java, PerfJexl2.java, PerfJexl3.java, PerfJexl3.java
>
>
> Compared to JEXL 2.1.1, arithmetic operations are slower in 3.0.
> The culprit is the logic around operators overloading; when the JexlArithmetic does not overload any operator, discovering whether it overloads one is repeated each time an interpreter is created (which is a costly introspection operation).
> As a workaround, one ca use an arithmetic that does overload an operator (for instance size) as in:
> {code}
> public static class JMeterArithmetic extends JexlArithmetic {
> public JMeterArithmetic(boolean astrict) {
> super(astrict);
> }
> /**
> * A workaround to create an operator overload
> * @param jma an improbable parameter class
> * @return 1
> */
> public int size(JMeterArithmetic jma) {
> return 1;
> }
> }
> {code}
> And use an instance of that class at engine creation time as in:
> {code}
> JexlEngine jexl = new JexlBuilder()
> .cache(512)
> .silent(true)
> .strict(true)
> .arithmetic(new JMeterArithmetic(true))
> .create();
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)