Grouper Users - Open Discussion List

[Shilen Patel <>]

Yes, that seems slow.  I don’t think the number of actions would be a problem.  If you haven’t analyzed your tables recently, I’d try that first.  If that doesn’t fix it, perhaps make the web service call on a test instance of the web service configured to use p6spy by setting the p6spy driver in grouper.hibernate.properties and then configuring spy.properties.  That might help determine if there’s a slow sql query.

Thanks!

- Shilen

From: Julio Polo <>
Date: Wednesday, March 25, 2015 at 11:46 PM
To: "" <>
Subject: [grouper-users] getPermissionAssignments is slow

Is 2.3 seconds considered unusually slow for a web service call to getPermissionAssignmentsLite?

We are using Grouper permissions for access control to a PHP app, and those 2.3s are quite noticeable at each click.

We only have one stem with three attribute definitions, and I'm providing that in the call. Here is what I'm sending via REST and XML:

          'action' => 'someActionString',
          'permissionType' => 'role_subject',
          'roleName' => 'STEM:FOR:APP:permissions:roles:admins',
          'wsSubjectId' => '99999999',
          'wsAttributeDefNameName' => 'STEM:FOR:APP:permissions:resources:app',
          'wsAttributeDefName' => 'STEM:FOR:APP:permissions:definitions:app'

The results come back in 2315 milliseconds:

         'responseMetadata' => {
                                'serverVersion' => '2.1.5',
                                'millis' => '2315',
                                'resultWarnings' => {}
                              }

For comparison, a similar query with permissionType='role' comes back in 409 millis.

Could it be that I have too many actions?  I have 40 actions defined for the above permission.  The other two permissions have 51 and 29 actions respectively.

Julio Polo
Enterprise Middleware, Identity and Access Management
Information Technology Services
University of Hawaii