Return to Jive Software

Skip navigation
Up to Discussions in Developers
1,406 Views 2 Replies Last post: Nov 17, 2009 11:33 AM by jbradley RSS
jbradley Novice
jbradley
60 posts since
Mar 24, 2009
Currently Being Moderated

Nov 17, 2009 7:37 AM

User container cache - 2% effectiveness

Hi Jive,

 

Product: SBS-public 3.0.8

 

We have been tweaking our production cache settings, and the 'user container cache' has caught our eye.

 

We have our cache preset at large. The user container cache defaults to 2 MB at this preset. However, the cache's effectiveness was 3%. So we increased the max size by a factor of 33, to 70 MB.

 

This morning the user container cache is showing 2% effectiveness again:

 

Cache Name Max Size Current Size Percent Used Effectiveness*
User Container Cache
70.00 MB40.68 MB58.1%2.0%

 

 

Do you know what could cause this cache to have such a low effectiveness, and how we can correct it? Our jiveUser table has about 1.2 million records.

 

 

Thanks,

jb

CurtisG Jive Employee
CurtisG
5,505 posts since
Aug 2, 2007
Currently Being Moderated
Nov 17, 2009 10:15 AM in response to: jbradley
Re: User container cache - 2% effectiveness

jb,

 

The User Container is fairly minimal information that is tied to any user in the system.  A low effectiveness here just means that you have a ton of users on the site that - but are possibly only viewing their own blog / profile 1 time (causing a miss in the cache) and then not returning to view it again until is has left the cache again.  I wouldn't expect any degradation in performance due to a low effectiveness as the query behind any user-container call is going to be very fast.

 

My recommendation would be to lower it back to a smaller number as it is storing information that is just taking up space that could be used for more effective and full caches.

 

-Curtis

jbradley Novice
jbradley
60 posts since
Mar 24, 2009
Currently Being Moderated
Nov 17, 2009 11:33 AM in response to: Curtis Gross
Re: User container cache - 2% effectiveness

Ok, thanks Curtis, this makes sense.

More Like This

  • Retrieving data ...

Bookmarked By (0)

To better serve our customers we have included functionality to automatically follow up on a case after it has been idle for more than 5 days, and then auto close after an additional 3 days of inactivity. Choose No to acknowledge that this case will remain idle for longer than 5 days.
Making cases public allows other customers to learn from the solution of the case. It can also be used to gain feedback from others in the community. Ask our Support Engineers for more info, but we encourage you to make your cases public.