Return-Path: Delivered-To: apmail-roller-user-archive@www.apache.org Received: (qmail 94815 invoked from network); 12 Aug 2010 17:05:47 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 12 Aug 2010 17:05:47 -0000 Received: (qmail 75996 invoked by uid 500); 12 Aug 2010 17:05:47 -0000 Delivered-To: apmail-roller-user-archive@roller.apache.org Received: (qmail 75882 invoked by uid 500); 12 Aug 2010 17:05:46 -0000 Mailing-List: contact user-help@roller.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@roller.apache.org Delivered-To: mailing list user@roller.apache.org Received: (qmail 75874 invoked by uid 99); 12 Aug 2010 17:05:46 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Aug 2010 17:05:46 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,SPF_HELO_PASS,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Aug 2010 17:05:41 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1OjbDV-0008S3-AC for user@roller.apache.org; Thu, 12 Aug 2010 10:05:21 -0700 Message-ID: <29420928.post@talk.nabble.com> Date: Thu, 12 Aug 2010 10:05:21 -0700 (PDT) From: fcai To: user@roller.apache.org Subject: Re: It is kind of slow In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: fcai@foreverliving.com References: <29392760.post@talk.nabble.com> Thanks for input. It looks like a DB2 issue which is caused by long sql statement in app. After Tune up DB and the performence is back up. Hassan Schroeder-2 wrote: > > On Wed, Aug 11, 2010 at 12:24 AM, Rajesh G > wrote: >> Well you can identify why it is slow using YSlow: > > YSlow is not made to diagnose problems like the OP describes (an > intermittent unresponsiveness on the server side). > >> I have downloaded Roller 4.01 recently and set it up on Tomcat 5.5 with >> Java >> 1.5 and DB2 version 9. > > Old version of Tomcat, old version of Java, incomplete versions , no > configuration info -- not particularly useful. And I know nothing about > DB2, so ... > >> Some time, not all the time, it is getting very slow and I have to wait >> for >> 10-20 seconds to get my request back. > > Profile your app. You could have too little/too much memory allocated > and that pause is GC going on. Or it could be something else running > on the box taking resources. Or the DB has stopped responding. Or > you've exhausted the DB connection pool, or any number of things... > > FWIW, > -- > Hassan Schroeder ------------------------ hassan.schroeder@gmail.com > twitter: @hassan > > -- View this message in context: http://old.nabble.com/It-is-kind-of-slow-tp29392760s12275p29420928.html Sent from the Roller - User mailing list archive at Nabble.com.