Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 95106 invoked from network); 7 Jan 2009 22:32:36 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 7 Jan 2009 22:32:36 -0000 Received: (qmail 12799 invoked by uid 500); 7 Jan 2009 22:32:24 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 12773 invoked by uid 500); 7 Jan 2009 22:32:24 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 12762 invoked by uid 99); 7 Jan 2009 22:32:24 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Jan 2009 14:32:24 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of billdsd@gmail.com designates 209.85.198.241 as permitted sender) Received: from [209.85.198.241] (HELO rv-out-0708.google.com) (209.85.198.241) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Jan 2009 22:32:16 +0000 Received: by rv-out-0708.google.com with SMTP id c5so8602655rvf.24 for ; Wed, 07 Jan 2009 14:31:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=tTRc3U5Z9z5Xx5KPVGid6mvK4no7Nr/8MFx3FcJ4F1A=; b=uf3wW890PIwatMOkdBz7ZjApHdSrqEVtqgcXncTguWCzplklb+huX+d3p+yuneuXM/ jgSBKoHRAg8Eiqz1wiIlFyuiWeaynV/WILX8PvJcH0qDeuhacPt7O8n8X7OLWHRAVk94 pY3Yu+ImV+Qbu0mZ447WKGk1fSEo8F8CtFq1w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=FiFbpZFxk2nMM9J82JAJKsvEoHhKpkphI3r2z0kriVrnGvmlOFHy4gxTTofMbUhFEQ rLVWbNNBdkEmFF62DBG22yn1FhG8jR7owV2i43FPZT5uWo00pJ1zmLlUlIYkVJ6uHzOf 1jmefhDMsoxwAnKl5tUYePSsGcGZpTNBqzVlE= Received: by 10.141.29.21 with SMTP id g21mr11718736rvj.198.1231367516102; Wed, 07 Jan 2009 14:31:56 -0800 (PST) Received: from ?192.168.1.14? (wsip-68-105-254-142.sd.sd.cox.net [68.105.254.142]) by mx.google.com with ESMTPS id g14sm25183732rvb.0.2009.01.07.14.31.54 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 07 Jan 2009 14:31:55 -0800 (PST) Message-ID: <49652D59.5050609@gmail.com> Date: Wed, 07 Jan 2009 14:31:53 -0800 From: Bill Davidson User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: Tomcat Users List Subject: Re: Oracle database calling the web app? References: <4963D9BC.7040302@gmail.com> <49652B20.7010001@iki.fi> In-Reply-To: <49652B20.7010001@iki.fi> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Juha Laiho wrote: > However, have you actually measured how much load it would put to various > pieces of your system to not cache this data, but just fetch it from the > DB more or less each time it is needed? > We currently have the ability to turn the caching on or off. We generally only turn it on when we anticipate a massive traffic storm coming to our site (caused by new highly in demand items going on sale). At the moment, once we turn the cache on, the cached data only gets updated by turning caching off and then back on -- which is something we don't like to do when we are getting thousands of hits per minute. While I'm not aware of exact measurements, the system can handle major traffic loads much better when we have the caching on. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org