Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 59951 invoked from network); 20 Oct 2005 21:53:14 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 20 Oct 2005 21:53:14 -0000 Received: (qmail 60349 invoked by uid 500); 20 Oct 2005 21:53:13 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 60293 invoked by uid 500); 20 Oct 2005 21:53:12 -0000 Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@forrest.apache.org List-Id: Delivered-To: mailing list dev@forrest.apache.org Received: (qmail 60282 invoked by uid 99); 20 Oct 2005 21:53:12 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [192.87.106.226] (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Oct 2005 14:53:10 -0700 Received: from ajax.apache.org (ajax.apache.org [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id 027C3514 for ; Thu, 20 Oct 2005 23:52:45 +0200 (CEST) Message-ID: <583349004.1129845164983.JavaMail.jira@ajax.apache.org> Date: Thu, 20 Oct 2005 23:52:44 +0200 (CEST) From: "Ross Gardler (JIRA)" To: dev@forrest.apache.org Subject: [jira] Updated: (FOR-711) Cache results from the Locationmap In-Reply-To: <559733227.1129842344788.JavaMail.jira@ajax.apache.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/FOR-711?page=all ] Ross Gardler updated FOR-711: ----------------------------- Description: Now that we are using the locationmap extensively it is showing up just how innefficient it is. The problem is that for the majority of requests there are multiple reqeuests to the locationmap. We can make things much faster (especially on the first page request) by caching results in the locationmap. I think a simple cache will sufice, lets just provide a static hashmap using the hint as a key and, of course, the location as the value. If we test all locationmaps and find no result we should record that tere is no result in this hashmap. This will also be a good place to throw an exception so that Cocoon can better report such errors (see FOR-701) was: Now that we are using the locationmap extensively it is showing up just how innefficient it is. The problem is that for the majority of requests there are multiple reqeuests to the locationmap. We can make things much faster (especially on the first page request) by caching results in the locationmap. I think a simple cache will sufice, lets just provide a static hashmap using the hint as a key and, of course, the location as the value. > Cache results from the Locationmap > ---------------------------------- > > Key: FOR-711 > URL: http://issues.apache.org/jira/browse/FOR-711 > Project: Forrest > Type: Sub-task > Components: Locationmap > Reporter: Ross Gardler > Priority: Critical > Fix For: 0.8-dev > > Now that we are using the locationmap extensively it is showing up just how innefficient it is. The problem is that for the majority of requests there are multiple reqeuests to the locationmap. We can make things much faster (especially on the first page request) by caching results in the locationmap. > I think a simple cache will sufice, lets just provide a static hashmap using the hint as a key and, of course, the location as the value. > If we test all locationmaps and find no result we should record that tere is no result in this hashmap. This will also be a good place to throw an exception so that Cocoon can better report such errors (see FOR-701) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira