Some numbers from a test instance of 4.2.0: Mem(MB) #TGTs #STs 2.39 500 0 4.72 500 500 4.79 1000 0 9.44 1000 1000 9.57 2000 0 18.87 2000 2000
This is Entry Memory from the Hazelcast management console. The regression is very linear: memory(MB) = 0.00465504762 * #TGTs + 0.0047840476 * #STs + 0.0025 The intercept value is somewhat less than its standard deviation, so the line may as well go through zero. Tom. On 04/15/2016 07:51 AM, Tom Poage wrote: > Morning, > > Before we launch into this, has anyone estimated memory requirements for > Hazelcast (community) by number of users and usage patterns of their > population? We're prepping 4.2 for deployment, and switching from Ehcache to > Hazelcast. > > E.g. our current TGT time-to-live is 12 hours. Over the course of a semi-busy > day we might get 80k logins. I estimate the average user logs into 2.5 > applications (though perhaps a handful of times each, depending on > application session duration) over the course of a day. > > Memory use for Hazelcast might then be roughly the sum of (serialized or > binary?) objects: > > hazelcast-overhead-factor * #users * ( size(TGT) + size(attributes) + > #services * size(ST) ) > > Thanks! > Tom. > -- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/a/apereo.org/group/cas-user/. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/57154EDA.5020301%40ucdavis.edu. For more options, visit https://groups.google.com/a/apereo.org/d/optout.
