Return-Path: Delivered-To: apmail-continuum-dev-archive@www.apache.org Received: (qmail 45665 invoked from network); 16 Jun 2009 02:39:44 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 16 Jun 2009 02:39:44 -0000 Received: (qmail 86640 invoked by uid 500); 16 Jun 2009 02:39:55 -0000 Delivered-To: apmail-continuum-dev-archive@continuum.apache.org Received: (qmail 86548 invoked by uid 500); 16 Jun 2009 02:39:55 -0000 Mailing-List: contact dev-help@continuum.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@continuum.apache.org Delivered-To: mailing list dev@continuum.apache.org Received: (qmail 86538 invoked by uid 99); 16 Jun 2009 02:39:55 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Jun 2009 02:39:55 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of odeaching@gmail.com designates 74.125.92.149 as permitted sender) Received: from [74.125.92.149] (HELO qw-out-1920.google.com) (74.125.92.149) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Jun 2009 02:39:47 +0000 Received: by qw-out-1920.google.com with SMTP id 4so2164860qwk.14 for ; Mon, 15 Jun 2009 19:39:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type; bh=Uk/50Y3lDLGMeXxyOT8noDUXSfsDr+Vn69WOVs1irYc=; b=UDAQPH6Lu0xXnS+Rccz/brZ35aIyyj9U5vIjZbk9OMeG+MgWwXHOC6giHlkB04/pUk 8ZC7yeRF54wmj2Lk0X/ID2FubMX3H2+bi2RUqWFVoX9XYLtZE8FjrhLE4hGO6zTXCc1m o7OukDBBvZLfNJhRgfmHBOO8Ed8DZJxNvEG94= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=ooUSKRZFpgKO9ygvX4xzb8RL9rwVA5VCg5huru7v/AOsW9RyJ6lzz0l/hr9yeja7hX 5DvS/WBdR1X4DlmCO/Um0OXt3vhlfMjwnR54QQ44tRMmkdlN32H4J5GqvkzzIxIk6336 r++vVCEisbdXGIVOTb5HUBLxhlxbC8cad/Klc= MIME-Version: 1.0 Sender: odeaching@gmail.com Received: by 10.229.80.73 with SMTP id s9mr38711qck.56.1245119966366; Mon, 15 Jun 2009 19:39:26 -0700 (PDT) In-Reply-To: References: <5F1CA506-F0F2-4370-BF8B-1FC2E858E9FA@apache.org> Date: Tue, 16 Jun 2009 10:39:26 +0800 X-Google-Sender-Auth: 2a8238befe8b7805 Message-ID: <8667b1bd0906151939w186a029doc62745ad44b10a57@mail.gmail.com> Subject: Re: Adding project groups takes longer and longer From: Deng Ching To: dev@continuum.apache.org Content-Type: multipart/alternative; boundary=0016361e812c4c5296046c6e1598 X-Virus-Checked: Checked by ClamAV on apache.org --0016361e812c4c5296046c6e1598 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I also noticed the cache is reset everytime a new "resource" (e.g. project) is created. This means the cache is cleared then all the roles/permissions are queried again from the database and added to the cache. The reason behind this is probably for the redback custom tags used in the jsps, I think it uses the permissions in the cache to check whether the user should be able to access specific functionalities.. Thanks, Deng 2009/6/16 Jos=E9 Morales Mart=EDnez > When we create a projectgroup create a set of roles with their permission= s. > > In my case I have created 56 groups and 1186 security_permissions with 13= 48 > security_role_permission_map and each time we create a projectGrup creat= e > 21 entries in security_permissions and 24 in > security_role_permission_map per projectgroup again. > > This problem occurs when creating the new permissions / roles, but the ma= in > problem occurs when you first run the method 'isAuthorized > (projectGroup.getName ())' to list the > results projectgroups in GroupSummaryAction. > ________________________________________ > De: Marica Tan [marica.tan@gmail.com] > Enviado el: martes, 16 de junio de 2009 1:40 > Para: dev@continuum.apache.org > Asunto: Re: Adding project groups takes longer and longer > > Here's what happens in GroupSummaryAction: > > 1. Get all project group --> query > 2. Loop through each group > - Check if user is authorized to view the project group --> query > - If authorized, then get project group summary --> query > > > -- > Marica > > On Tue, Jun 16, 2009 at 7:25 AM, Brett Porter wrote: > > > That's insane. > > > > Is this all in the process of adding, or is a large portion coming from > the > > group summary pages again? > > > > - Brett > > > > > > On 16/06/2009, at 6:56 AM, Wendy Smoak wrote: > > > > On Mon, Jun 15, 2009 at 9:39 AM, Wendy Smoak wrote: > >> > >> To try to reproduce that, I added 400 groups to a fresh Continuum > >>> 1.3.3 instance. I notice that it takes longer and longer to add each > >>> group. Here's a graph: > >>> > >>> > http://people.apache.org/~wsmoak/continuum/continuum-1.3.3-add-400-groups= .png > < > http://people.apache.org/%7Ewsmoak/continuum/continuum-1.3.3-add-400-grou= ps.png > > > >>> > >> > >> Back to the "too many queries" idea, I found that > >> - adding group401 resulted in 61,144 queries > >> - adding group402 restulted in 61,278 queries > >> > >> -- > >> Wendy > >> > > > > > > ______________________ > Este mensaje, y en su caso, cualquier fichero anexo al mismo, > puede contener informacion clasificada por su emisor como confidencial > en el marco de su Sistema de Gestion de Seguridad de la > Informacion siendo para uso exclusivo del destinatario, quedando > prohibida su divulgacion copia o distribucion a terceros sin la > autorizacion expresa del remitente. Si Vd. ha recibido este mensaje > erroneamente, se ruega lo notifique al remitente y proceda a su borrado. > Gracias por su colaboracion. > ______________________ > This message including any attachments may contain confidential > information, according to our Information Security Management System, > and intended solely for a specific individual to whom they are addressed= . > Any unauthorised copy, disclosure or distribution of this message > is strictly forbidden. If you have received this transmission in error, > please notify the sender immediately and delete it. > ______________________ > --0016361e812c4c5296046c6e1598--