Version 3


    There may be times when your Jive community sees a sudden increase in traffic and usage. This can be due to company announcements, CEO blog posts, or inviting the entirety of your organization to join your Jive community.


    To ensure that the Jive community web application continues to be responsive and provides an acceptable experience, it is advised that you perform coordinated load testing based on expected traffic in order to verify that you have allocated sufficient hosting resources to support your expected traffic volume. There are some tips outlined below for what a community manager can do to prepare for this type of event.


    Jive Hosting Notification

    If you are a Jive hosted customer and you are expecting a sudden increase or change in traffic volume then it is recommended that you first create a new support case at least one week in advance with details around the expected traffic patterns and timing of the event.


    Jive's Hosted and Cloud environments are built and configured around customer's expected and forecasted traffic and usage patterns, so if there is a planned upcoming change in your traffic patterns then providing advanced notice to Jive Hosting will allow the team to accommodate for the upcoming event. Our hosting team will review this information along with your site's configuration to make sure that the correct hosting resources are in place to support your community's traffic.


    On Premise Load Testing

    If you are running an on-premise instance it is recommended that you perform load testing to check that your allocated server hardware can support your expected traffic. You will want to review the Hardware Requirements section of our product documentation  and verify that your server hardware meets the minimum requirements. It may be necessary to temporary add additional web application nodes to your infrastructure in order to support the additional traffic.


    Tips for reducing Jive load temporarily


    There are some basic recommendations Jive will make to community managers when preparing for an upcoming increase in Jive usage


    1. Stagger site announcements over time. If you are inviting a large volume of people to Jive via an email newsletter, it is recommended that you stagger the delivery of these email notifications over a series of hours or days so that the traffic increase to your Jive community is evenly spread out.
    2. Avoid sending site announcements during peak hours.  Similar to the previous note, its advised to avoid sending announcements to all users during peak hours of usage (Early in the morning, After lunch, etc). It's best to analyze traffic patterns of your community to better understand when your site is already experiencing the most traffic.
    3. Limit use of dynamic widgets like Recent Activity on the event's landing page. Widgets like the Recent Activity widget can use significant amount of resources if your site is under sudden heavy load. If you are linking users directly to a page that has a widget like this it is advised that you redesign your overview page layout to minimize the use of these widgets


    Hosted and On-Premise System Property Configuration Changes

    There are several system properties available to Hosted and On-Premise customers that can be changed to improve site performance during major events:



    Impact Level




    1Lower the pagination / threaded threshold

    Set system property (default = 100),

    thread.allMessageActions.messageLimit = 50

    No restart required

    Discussion replies will have no indentation and not all replies will appear on the same page.
    2Turn off activity tracking

    Set system property,

    jive.activity.tracker.enabled = false

    No restart required

    Quality of recommendations may decrease.
    3Extend activity polling interval

    Set system property, = match your session timeout

    This should equal auth.lifetime. By default, they are 5 minutes / 300000 milliseconds so if you want the session time out to be 60 minutes, you would set the property to be 3600000 milliseconds.


    No restart required

    Users won't be notified of new activity as frequently
    4Turn off Read Tracking

    Toggle the radio control in the admin console at System -> Settings -> Discussions.


    No restart required.

    Users won't be able to discern read from unread discussions on a place's content page:

    Screen Shot 2015-10-19 at 3.06.35 PM.png

    5Turn off activity polling

    Set system properties,

    jive.activity.counts.all = false

    jive.activity.counts.custom = false

    No restart required

    Removal of notifications of new activities


    6Turn off Structured Outcomes

    Toggle the radio control in the admin console at System -> Settings -> Structured Outcomes.


    No restart required.


    For Jive 7.x instances or earlier, the system property must be set:

    outcomes.enabled = false

    outcomes.enabledAction links will go away in the Jive UI: