Enterprise 3.x
  1. Enterprise 3.x
  2. ETHREEOH-2046

Activity feed causing high load on db for user activity for sites with high # of members

    Details

    • Type: Improvement Improvement
    • Status: Closed Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 3.1 SP1
    • Fix Version/s: Pending
    • Component/s: Share
    • Security Level: external (External user)
    • Labels:
      None
    • Environment:
      3 systems with equal system config: 2 x 2.66 GHz processors, 3 GB RAM .... share / repository / database ...
      Share + Repo is: Java 1.6.0_10, Tomcat 6.0 (alfresco+tomcat bundle).
      Mysql: 5.0.45

      Description

      Currently on share.alfresco.com we have the 'community' site which has 24k + members. The activity feed for user join/leave etc. Causes high load on db due to (seemingly) multiple insert activity. This makes the feed for this use case effectively unusable, as we get joins every 5 minutes or so.

      Workaround (from Jan) is that I've removed the ftl files for the user activities (plus the generic one so it doesn't fall through) ... this effectively disables this type of feed. Instead we simply get an error message stating missing file - which is fine for now.

      We also see this similar activity due to other activity types, but user join is the most common and the biggest problem.

        Activity

        Hide
        Ken Barber added a comment -
        To add - this also causes problems for documentLibrary activity when something from marketing modifies a document, of course this occurs less frequently.
        Show
        Ken Barber added a comment - To add - this also causes problems for documentLibrary activity when something from marketing modifies a document, of course this occurs less frequently.
        Hide
        Steve Rigby added a comment -
        BRB reviewed
        Show
        Steve Rigby added a comment - BRB reviewed

          People

          • Assignee:
            Closed Bugs
            Reporter:
            Ken Barber
          • Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:
              Date of First Response:

              Time Tracking

              Estimated:
              Original Estimate - 2 weeks
              2w
              Remaining:
              Remaining Estimate - 2 weeks
              2w
              Logged:
              Time Spent - Not Specified
              Not Specified