Return-Path: Delivered-To: apmail-continuum-dev-archive@www.apache.org Received: (qmail 36592 invoked from network); 16 Jun 2009 02:25: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:25:44 -0000 Received: (qmail 75432 invoked by uid 500); 16 Jun 2009 02:25:55 -0000 Delivered-To: apmail-continuum-dev-archive@continuum.apache.org Received: (qmail 75346 invoked by uid 500); 16 Jun 2009 02:25: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 75336 invoked by uid 99); 16 Jun 2009 02:25: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:25: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.148 as permitted sender) Received: from [74.125.92.148] (HELO qw-out-1920.google.com) (74.125.92.148) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Jun 2009 02:25:47 +0000 Received: by qw-out-1920.google.com with SMTP id 4so2161852qwk.14 for ; Mon, 15 Jun 2009 19:25: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=fwSOk0tjdrWNr/mpgnGuOOBIhi3h5PlyUsn4nrFU3A0=; b=DyVRG4Dt65bVdP+smM2ZDQ8iivMh6Ii0BttJt5MGdwsFWXL+GzEShNnNQmm5n066uw dA7o7zbl92JiRhS7qDc6f37wmgQ3xL6PDUohN4ySvt1++KdkRZNZqw3XXKdq4nGVKmkD TH6sQR1GlKRZjgEaTP/wCLmkjVgcMgrj7B5dE= 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=EPtl0z+9BxupDoic/VCRi30Ca5teOnb0T3zF0mQ512kniM0F4z3pN0NYPgvYG6SQyj RlXxLW/s5q9nA1vuRjWZ7klFKjHwQQOpPAupw86gnQm1xdSPLjMNOnqGvmucSC0G/ZOk a+zxN1Hn4Wr+d416ynBkDeHiw7vMYG4ES+EuI= MIME-Version: 1.0 Sender: odeaching@gmail.com Received: by 10.229.70.138 with SMTP id d10mr1477091qcj.22.1245119126688; Mon, 15 Jun 2009 19:25:26 -0700 (PDT) In-Reply-To: References: Date: Tue, 16 Jun 2009 10:25:26 +0800 X-Google-Sender-Auth: 5f639f3903806734 Message-ID: <8667b1bd0906151925y12735d50kaabc6b7bc47c6041@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=0016360e3d183fd482046c6de34f X-Virus-Checked: Checked by ClamAV on apache.org --0016360e3d183fd482046c6de34f Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On Tue, Jun 16, 2009 at 4:51 AM, Wendy Smoak wrote: > The actual system with the performance problem is using MySQL, however > these results and the graph were from a fresh 1.3.3 instance using the > embedded Derby database. > > Another use case that is slow is simply logging in. I've personally > timed it at 3 minutes from clicking the button to log in, before I see > the next page rendered. > > Brett suggested turning on the JPOX sql query logging, and here's what > I see while logging in as admin: > > Continuum 1.3.3 with 20 project groups - 3,192 SELECT queries > Continuum 1.3.3 with 400 project groups - 60,184 SELECT queries > > It's not especially slow to log in as admin (5-6 seconds) with 400 > project groups, but this is with an embedded Derby db, so the queries > aren't going out on the network. > > In any case, why does it need to do *that* many queries simply to > process a login? One of these many queries I saw yesterday from the logs was due to the cache being reset during each login. The cache is cleared first then all the roles/permissions are queried and added to the cache. Since we're using resource-based roles, it takes longer to process the login if there are a lot of resources (e.g. projects).. - Deng > > > -- > Wendy > > On Mon, Jun 15, 2009 at 11:58 AM, Emmanuel > Venisse wrote: > > It's very bad. > > > > Do you use an embedded derby DB or an external? I don't think it is good > to > > use an embedded DB for a "big" DB. > > > > Emmanuel > > > > On Mon, Jun 15, 2009 at 6:39 PM, Wendy Smoak wrote: > > > >> I've noticed Continuum getting slower and slower... we're trying to > >> track down exactly why, but one theory relates to there being lots of > >> user roles that have to be checked, which would mean there are lots of > >> project groups. > >> > >> 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-groups.png > > > >> > >> On trunk it's similar. There in the audit log I can see there are 3 > >> seconds between adding the second and third groups, and 19 seconds > >> between groups 399 and 400. All in all it takes over an hour to add > >> 400 groups to an instance. > >> > >> The test code is in the sandbox: > >> > >> > http://svn.apache.org/repos/asf/continuum/sandbox/continuum-webapp-test-many-roles/ > >> > >> Any ideas? Are we missing an index on some field? > >> > >> -- > >> Wendy > >> > > > --0016360e3d183fd482046c6de34f--