This site is scheduled for a small content update on Tuesday, January 22nd, between the hours of 5:00pm and 8:00pm Pacific Time (Jan 23 01:00 – Jan 23 4:00 UTC). Access to this site may be slightly delayed during that time.

Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.
  • London
  • Kingston
  • Jakarta
  • Istanbul
  • Helsinki
  • Geneva
  • Store

Homepage caching notes and limitations

Log in to subscribe to topics and get notified when content changes.

Homepage caching notes and limitations

Review these notes and limitation when configuring homepage caching.

  1. Instances with less than one hundred or so concurrent users should not expect to see a significant benefit to this feature in most real-world scenarios. Homepage visits in these situations are infrequent enough that most widgets will have aged out of the cache before a second user visits a homepage. If you do not experience performance problems with your homepages, tweaking the behavior of this cache is not recommended.
  2. The homepage cache is segmented by company, domain, and roles, so users with different rights and visibility into the system cannot see each other's data by pulling it out of the cache. This does, however, mean that cache efficiency will be lower for instances that make extensive use of domain separation.
  3. In an environment with a cluster of multiple UI nodes (as opposed to a UI node and worker configuration), each node has its own homepage cache. Entries are removed from the homepage cache only when their data changes on the node upon which they are cached. Entries are always removed from the cache when they expire.