By: Roman Ott user 05 Jun 2019 at 9:33 a.m. CDT

4 Responses
Roman Ott gravatar
Hello Dear Gluu-Team, we use Gluu as Identity Provider for webapplications with high transaction volume. Often we have problem with a patch request to a gluu member group with many users, our basic group. We submit a normal patch request via guzzle client (timeout 30 seconds) and we often reach this timeout. Is there a bug that patch requests to groups with many members took a long time or is it normal? This is an example of our request array ( [schemas] => Array ( [0] => urn:ietf:params:scim:api:messages:2.0:PatchOp ) [Operations] => Array ( [0] => Array ( [op] => add [path] => members [value] => Array ( [0] => Array ( [value] => {PLACEHOLDER_FOR_USER_INUM} ) ) ) ) )

By William Lowe staff 05 Jun 2019 at 9:45 a.m. CDT

William Lowe gravatar
Hi Roman, This type of advances debugging is outside the scope of community support. It would be covered under VIP support. If you'd like to discuss, just [schedule a call](https://gluu.org/booking). I also removed some of the identifying details from your request. Thanks, Will

By Roman Ott user 05 Jun 2019 at 10:30 a.m. CDT

Roman Ott gravatar
Alright, thank u. My question was only: Is long processing time normal for patchGroup request via scim for groups with a large amount of users or not. I dont want an analyze of the error or something else. Here it is clear that we need VIP Support.

By Jose Gonzalez staff 05 Jun 2019 at 11:21 a.m. CDT

Jose Gonzalez gravatar
> Is long processing time normal for patchGroup request via scim for groups with a large amount of users or not Probably: patch having a lot of computing overhead associated. Also it is different to apply 1 add operation passing an array of _n_ elements than applying *n* adds supplying a singleton array - the latter being more expensive. This is something that requires your own insight if you continue with community usage

By Roman Ott user 11 Jun 2019 at 2:11 a.m. CDT

Roman Ott gravatar
Thx a lot and Best Regards