Kuali Rice Development
  1. Kuali Rice Development
  2. KULRICE-7139

Role service does not seem to have caching any more

    Details

    • Type: Bug Fix Bug Fix
    • Status: Closed Closed
    • Priority: Blocker Blocker
    • Resolution: Duplicate
    • Affects Version/s: 2.0, 2.0.1, 2.0.2
    • Fix Version/s: Not version specific
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-3768Add more persistent cache of RoleImpl data in RoleServiceImpl
      KULRICE-2310Create cache of person data local to Rice
      KULRICE-3726Add caching of role members loaded from the database
      KULRICE-5967Investigate whether we should publish methods on services to flush caches
      KULRICE-4395addMember via the Role Screen does not work with external identity service
      KULRICE-2452Implement cluster-aware caching on KNS System Parameters
      KULRICE-8714Bug related to caching used to improve role service performance.
      KULRICE-7541Condition-based caching annotations on PermissionService are incorrect
      KULRICE-5638Figure out how to make caching possible for services in the core module
      KULRICE-2315Implement caching of data to the IdentityManagementService implementation
    • Rice Module:
      KIM
    • Application Requirement:
      KFS
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      Since the removal of the RoleManagementServiceImpl, there seems to be no caching any more on the main KIM role service. This is necessary to maintain system performance for some base KNS/KRAD checks.

      For example - the asset lookup performs the same set of checks for every single row of the lookup results. I've noticed this in other places as well.

      We had some semi-intelligent caching before under Rice 1.0. From a performance standpoint, I feel this is a blocker for the KFS upgrade. All is well when running a local MySQL database, since the queries are so rapid, but with a database on a separate machine, the network lag will kill performance.

        Issue Links

          Activity

          Hide
          Eric Westfall added a comment -

          Jonathan, I think this is a dupe of KULRICE-7127. Do you want to just go ahead and put a comment on that issue if you have anything additional to add? It already has a fix version of 2.0.2. Thanks.

          Show
          Eric Westfall added a comment - Jonathan, I think this is a dupe of KULRICE-7127 . Do you want to just go ahead and put a comment on that issue if you have anything additional to add? It already has a fix version of 2.0.2. Thanks.

            People

            • Assignee:
              Unassigned
              Reporter:
              Jonathan Keller
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Structure Helper Panel