Skip to Content.
Sympa Menu

grouper-users - Re: [grouper-users] Performance Issues With 1.2 rc3

Subject: Grouper Users - Open Discussion List

List archive

Re: [grouper-users] Performance Issues With 1.2 rc3


Chronological Thread 
  • From: "blair christensen." <>
  • To: "Shilen Patel" <>
  • Cc:
  • Subject: Re: [grouper-users] Performance Issues With 1.2 rc3
  • Date: Mon, 18 Jun 2007 11:51:09 -0500
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=lJEMsr4DVsudz1G9rzNeueN7TrT0gnY9P8hYlXp1qSYOuN85iXlk1KIjVuzonuMsChrplqBMZWzc85n5Kzljo+leNhy+eZT7FfRF8dm6izvBVj59Yx1k5GVW4Ns7/XM52hINrh/HgM4kh4Ql6H2K7j0XtO2DoDLolg7ZpP4McdI=
On 6/18/07, Shilen Patel
<>
wrote:
Our DBAs have added an index that significantly improves performance for
group and stem deletes in our environment. However, the stem deletes
are still much slower than what we saw in Grouper 1.1. We added an
index on the grouper_memberships table for the columns owner_id,
list_name, list_type, and mship_type.

Odd. All of those should already be indexed in 1.2.0rc3.

Is it possible that your db schema was not properly generated? Or
perhaps was generated using the wrong Hibernate dialect? It sounds
like you might be missing one (or more) other indexes that should have
been created by default.

Archive powered by MHonArc 2.6.16.

Top of Page