ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ali <alimovalis...@gmail.com>
Subject Index performance
Date Mon, 04 Dec 2017 13:36:31 GMT

I found poor sql index performance and CPU utilisation in ignite 2.3 version when try to benchmark
cluster for performance.

Cluster configuration:

6 x 2 E5-2600v2 256GB 10GB link
1 x 4 E7 node (edge) from which tests are running

Ignite config

<property name="cacheConfiguration">
    <bean class="org.apache.ignite.configuration.CacheConfiguration">
        <property name="name" value=“test"/>
        <property name="backups" value="0"/>
        <property name="atomicityMode" value="ATOMIC"/>
        <property name="cacheMode" value="PARTITIONED"/>
        <property name="copyOnRead" value="true"/>
        <property name="readFromBackup" value="true"/>
        <property name="queryParallelism" value=“48"/>
        <property name="rebalanceMode" value="ASYNC"/>
        <property name="statisticsEnabled" value="false"/>

        <property name="queryEntities">
                <bean class="org.apache.ignite.cache.QueryEntity">

                    <constructor-arg value="java.lang.String"/>
                    <constructor-arg value=“com.example.Test"/>

                    <property name="tableName" value=“Test"/>
                    <property name="fields">
                            <entry key=“field-1" value="java.lang.String"/>
                            <entry key=“field-2" value="java.lang.String"/>
                            <entry key=“field-3" value="java.lang.String"/>
                            <entry key=“field-4" value="java.lang.String"/>
                            <entry key=“field-5" value="java.lang.String"/>
                            <entry key=“field-6" value="java.lang.Long"/>

                    <property name="indexes">
                            <bean class="org.apache.ignite.cache.QueryIndex">
                                <property name="name" value="fields_idx"/>
                                <property name="fields">
                                        <entry key=“field-2" value="true"/>
                                        <entry key=“field-3" value="true"/>
                                        <entry key=“field-4" value="true"/>
                                        <entry key=“field-5" value="true"/>
                                        <entry key=“field-6" value="true"/>
                                <property name="inlineSize" value="24"/>
                                <property name="indexType" value="SORTED"/>


public Collection<Test> find(String mcc, String mnc, String lac, String cid, long lastSeenDt,
long offset, long limit) {
    SqlQuery<String, Test> qry = new SqlQuery<>(
            "select * from Test where field-2 = ? and field-3 = ? and field-4 = ? and field-5
= ? and field-6 >= ? limit ? offset ?"

    qry.setArgs(mcc, mnc, lac, cid, lastSeenDt, limit, offset);

    try (QueryCursor<Cache.Entry<String, Test>> query = cache.query(qry)) {
        return StreamSupport.stream(query.spliterator(), false)


Benchmark consist of several java processes that call this query through RMI  in {1..20 000}
threads but maximum CPU utilisation doesn’t increase more than 9% on each node and doesn’t
depend on load

simple IgniteCache#get test fully utilise CPU 

With best regards
Alisher Alimov

View raw message