forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thorsten Scherler (JIRA)" <>
Subject [jira] Commented: (FOR-711) Cache results from the Locationmap
Date Fri, 10 Feb 2006 12:26:58 GMT
    [ ] 

Thorsten Scherler commented on FOR-711:

El jue, 09-02-2006 a las 07:08 -0500, Tim Williams escribió:
> To both of you... Are these the documented issues or new ones?  If
> it's for FOR-732, for development purposes, just turn lm caching off
> in forrest-core.xconf for now.

Well that is the problem, the caching should be configurable in the
sitemap and not the xconf since IMO we should be able to use caching and
non-caching locationmap lookups. *Without* restarting forrest. ;-)

> Actually, if I hear no complaints, I'll turn it off by default until
> FOR-732 is resolved.

No, please let it on, but maybe give us some instructions how we can
configure it on a sitemap level (best as <map:pipe/>).

> Cache results from the Locationmap
> ----------------------------------
>          Key: FOR-711
>          URL:
>      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:
For more information on JIRA, see:

View raw message