Ignite C客户端模式，近缓存-Java 学习之路

我有一个以复制模式运行的点火服务器和同一节点上的许多客户端启用了近缓存 . 现在，当我运行具有近缓存且没有近缓存的客户端时，我没有发现显着的性能差异 .

我对近缓存的理解是经常使用的密钥和值将存储在客户端本身，因此不会对服务器进行实际的Get（）调用 . 如果我错了，请纠正我 .

有人可以共享一个工作的近缓存配置xml .

SERVER CONFIG:
<beans xmlns="http://www.springframework.org/schema/beans"
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xmlns:util="http://www.springframework.org/schema/util"
       xsi:schemaLocation="
        http://www.springframework.org/schema/beans
        http://www.springframework.org/schema/beans/spring-beans.xsd
        http://www.springframework.org/schema/util
        http://www.springframework.org/schema/util/spring-util.xsd">
        <bean id="grid.cfg" class="org.apache.ignite.configuration.IgniteConfiguration">

            <property name="cacheConfiguration">
                <bean class="org.apache.ignite.configuration.CacheConfiguration">
                    <property name="cacheMode" value="LOCAL" />
                                <!-- Enable near cache to cache recently accessed data. -->

                                <!--    <property name="nearConfiguration">

                                    <bean class="org.apache.ignite.configuration.NearCacheConfiguration"/>

                                </property> -->
                    <property name="nearConfiguration">
                    <bean class="org.apache.ignite.configuration.NearCacheConfiguration">
                    </bean>
                    </property>

                </bean>
            </property>
        <!-- Explicitly configure TCP discovery SPI to provide list of initial nodes. -->
        <property name="discoverySpi">
            <bean class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi">
                <property name="ipFinder">
                    <!--
                        Ignite provides several options for automatic discovery that can be used
                        instead os static IP based discovery.
                    -->
                    <!-- Uncomment static IP finder to enable static-based discovery of initial nodes. -->
                    <!-- <bean class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder"> --> 
                             <bean class="org.apache.ignite.spi.discovery.tcp.ipfinder.multicast.TcpDiscoveryMulticastIpFinder">  
                        <property name="addresses">
                            <list>
                                <!-- In distributed environment, replace with actual host IP address. -->
                                <!-- <value>127.0.0.1:48550..48551</value> -->
                                <value>XXX.ZZZ.yyy.36:47500..47501</value>  
                            </list>
                        </property>
                    </bean>
                </property>
            </bean>
        </property>

    </bean>
</beans>


CLIENT CONFIG:

<beans xmlns="http://www.springframework.org/schema/beans"
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xmlns:util="http://www.springframework.org/schema/util"
       xsi:schemaLocation="
        http://www.springframework.org/schema/beans
        http://www.springframework.org/schema/beans/spring-beans.xsd
        http://www.springframework.org/schema/util
        http://www.springframework.org/schema/util/spring-util.xsd">
        <bean id="grid.cfg" class="org.apache.ignite.configuration.IgniteConfiguration">

            <property name="cacheConfiguration">
                <bean class="org.apache.ignite.configuration.CacheConfiguration">
                    <property name="cacheMode" value="LOCAL" />
                                <!-- Enable near cache to cache recently accessed data. -->

                                <!--    <property name="nearConfiguration">

                                    <bean class="org.apache.ignite.configuration.NearCacheConfiguration"/>

                                </property> -->
                    <property name="nearConfiguration">
                    <bean class="org.apache.ignite.configuration.NearCacheConfiguration">
                    </bean>
                    </property>

                </bean>
            </property>
        <!-- Explicitly configure TCP discovery SPI to provide list of initial nodes. -->
        <property name="discoverySpi">
            <bean class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi">
                <property name="ipFinder">
                    <!--
                        Ignite provides several options for automatic discovery that can be used
                        instead os static IP based discovery.
                    -->
                    <!-- Uncomment static IP finder to enable static-based discovery of initial nodes. -->
                    <!-- <bean class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder"> --> 
                             <bean class="org.apache.ignite.spi.discovery.tcp.ipfinder.multicast.TcpDiscoveryMulticastIpFinder">  
                        <property name="addresses">
                            <list>
                                <!-- In distributed environment, replace with actual host IP address. -->
                                <!-- <value>127.0.0.1:48550..48551</value> -->
                                <value>XXX.ZZZ.yyy.38:47500..47501</value>  
                            </list>
                        </property>
                    </bean>
                </property>
            </bean>
        </property>


    </bean>
</beans>

1 回答

1
是的，靠近缓存通过在本地缓存节点上经常使用的条目来提高性能，但是如果在单机或JVM上运行所有测试则没有意义 . 近缓存不允许在远程节点上获取数据，但在测试中，一切都已在本地运行 .

对于 REPLICATED 或 PARTITIONED 缓存上的服务器节点，临近缓存也没有意义，其中备份数等于或大于数据节点数，因为所有数据集本地都可用于每个节点 .

因此，为了提高性能，您需要将客户机节点配置为使用Near缓存，此时服务器节点可在远程计算机上运行 . 测量前不要忘记在缓存附近预热 .

以下是用于设置Near缓存的XML代码段：
```
...
<bean class="org.apache.ignite.configuration.CacheConfiguration">

       

       <property name="nearConfiguration">
             <bean class="org.apache.ignite.configuration.NearCacheConfiguration"/>
       </property>
</bean>
...
```
回复于 2024-04-29T13:13:52+08:00

Ignite C客户端模式，近缓存

1 回答

相关问题