Why use shared cache?
There is no more efficient way to increase the scalable performance of applications then the use caching to unload deeper layers.
>> Shared Cache>> Shared Cache Config>> Configuration Client>> Client Distributed Caching
Client configuration for distributed caching
In Shared Cache Topology section we have listed advanteges of distributed caching. Lets assume we have 3 IIS WebServers in the same zone and we want to configure them for distributed caching where on each server an instance of indeXus.Net Shared Cache Server is installed.
Server details:
|
Server no. 1
|
Server no. 2
|
Server no. 3
|
-
Name: WebSrv20
-
IP: 192.168.1.20
|
-
Name: WebSrv30
-
IP: 192.168.1.30
|
-
Name: WebSrv40
-
IP: 192.168.1.40
|
Example of a client configuration file
The configuration below will distribute your data to the 3 configured server nodes. It could not be easier ;-)
<indexusNetSharedCache defaultProvider="IndexusSharedCacheProvider">
<clientSetting
SharedCacheVersionNumber="2.0.3.268"
LoggingEnable="1"
CompressionEnabled="0"
CompressionMinSize="1024000"
SocketPoolMinAvailableSize="5"
HashingAlgorithm="Hashing" />
<servers>
<add key="WebSrv20" ipaddress="192.168.1.20" port="48888" />
<add key="WebSrv30" ipaddress="192.168.1.30" port="48888" />
<add key="WebSrv40" ipaddress="192.168.1.40" port="48888" />
</servers>
<replicatedServers>
<!-- only use this node in case you are using replication mode on server -->
</replicatedServers>
<providers>
<add
name="IndexusSharedCacheProvider"
type=">
MergeSystem.Indexus.WinServiceCommon.Provider.
Cache.IndexusSharedCacheProvider,
MergeSystem.Indexus.WinServiceCommon"
</add>
</providers>
</indexusNetSharedCache>
|