CODEWITHSUNDEEP
.netcachingappfabric
user181799
user181799

Reputation:

Performance issues using AppFabric caching

I am finding that when AppFabric cache comes under heavy load it is resulting in unpredictable application behaviour.

Has anyone experienced anything similar? Any thoughts on ideal configuration for AppFabric?

Upvotes: 0

Views: 1829

Answers (2)

RohitK
RohitK

Reputation: 1

The maximum size of an object that can be cached by is 8 mb (by default). You can change it through advanced configuration properties if your production application is going to cache objects of that size. Regarding the other question: What happens if we try to pump 150 Mb data into cache of 128 Mb size. 1. The objects will get evitcted using a best effort LRU and newer objects will replace them. 2. If the incoming rate is faster than the rate of eviction, the cache might be throttled , blocking all writes for some duration.

Upvotes: 0

s1mm0t
s1mm0t

Reputation: 6095

It seems like the limits you have applied to AppFabric are the ultimate cause of your performance problem. That said, you may also want to ensure that you have configured the channelOpenTimeout and requestTimeout to some suitable values - the defaults are quite high and in many it cases it would be preferable to re-read the data from your data store rather than wait for AppFabric to respond.

  <dataCacheClient channelOpenTimeout="5" requestTimeout="1000">
    <!-- cache host(s) -->
    <hosts>
      <host name="localhost" cachePort="22233" />
    </hosts>
  </dataCacheClient>

Upvotes: 1

Related Questions