Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 26 Sep 2017 18:33:00 +0000 (UTC)
From: "xin jin (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.13105203.1506450750000.207583.1506450780040@Atlassian.JIRA>
In-Reply-To: <JIRA.13105203.1506450750000@Atlassian.JIRA>
References: <JIRA.13105203.1506450750000@Atlassian.JIRA> <JIRA.13105203.1506450750243@jira-lw-us.apache.org>
Subject: [jira] [Created] (CASSANDRA-13904) Performance improvement of
 Cassandra UDF/UDA
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Tue, 26 Sep 2017 18:33:04 -0000

xin jin created CASSANDRA-13904:
-----------------------------------

             Summary: Performance improvement of Cassandra UDF/UDA
                 Key: CASSANDRA-13904
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13904
             Project: Cassandra
          Issue Type: Improvement
          Components: CQL
            Reporter: xin jin
            Priority: Critical
             Fix For: 3.11.x


Hi All,

We have made a few experiments and found that running query with direct UDF=
 execution is ten time more faster than the async UDF execution. The in-lin=
e comment: "Using async UDF execution is expensive (adds about 100us overhe=
ad per invocation on a Core-i7 MBPr)=E2=80=9D https://insight.io/github.com=
/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/cql3/functions/U=
DFunction.java?line=3D293 show that this is a known behavior.  My questions=
 are as below:

1. What are the main pros and cons of these two methods? Can I find any doc=
uments that discuss this? =20

2. Are there any plans to improve the performance of using async UDF? A sim=
ple way come to my mind is to use some sort of batch method, e.g., replace =
current row by row method with some rows by some rows. Are there any concer=
ns on this?

3. How people solve this performance issue in general? It seems this perfor=
mance issue is not an urgent or an important issue to solve because it is k=
nown and it is still there. Therefore people must have some sort of good so=
lution solving this issue.=20

I really appreciate your comments in advance.

Best regards,

Xin


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org