Grouper Users - Open Discussion List

[Shilen Patel <>]

Do your membership changes often cause a lot of effective membership 
changes?  If so, that update statement would be updating a lot of 
groups.  Otherwise, have you tried to see if analyzing your tables 
(grouper_groups and grouper_group_set) helps?

Thanks!

-- Shilen

On 3/1/11 1:54 PM, Jim Fox wrote:
> A couple of weeks ago I activated the update of membership changes:
>
>     groups.updateLastMembershipTime = true
>
>
> This did update membership change times, but also caused a major
> hit on our postgres DBMS.  Response times on our web service
> went from 1-2 sec to 5-10 sec.  Looking at the database we saw
> continually running update statements like:
>
>     update grouper_groups set last_membership_change = $1 where id  in ($2, 
> $3...)
>
> As soon as one completed another started - or so it seemed.
> The load average on our DB server went from below 1 to above 7.
> Setting the updateLastMembershipTime back to false removed the
> update commands and immediately improved response times.
>
> This is standard grouper 1.6.0.  During normal daytime operations
> we see membership changes every five to ten seconds.
>
> Jim
>
>