Tim Williams wrote: > Anyone had a chance to check this out? I'll go ahead and apply it but > since some of the earlier problems only occurred under stress > conditions, I wanted to give an opportunity for others to test too.
I made some time to try it today. However i don't know what is a good test nor what to look for. Anyway i tried building the Forrest docs at "site-author" with the level for locationmap logging set to DEBUG. Before it took about 4 minutes to build. After adding your LM patch it takes about 2.5 minutes. Do you have a reference to the "stress conditions" that you refer to above? Do we need a default ehcache configuration file? Where does it get placed? Does that configuration file affect the main Cocoon cache which has some configuartion via main/webapp/WEB-INF/cocoon.xconf and main/webapp/WEB-INF/properties/core.properties ? Sorry for more questions rather than much help. -David > > [ > > https://issues.apache.org/jira/browse/FOR-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > > ] > > > > Tim Williams updated FOR-1031: > > ------------------------------ > > > > Attachment: lm_cache.diff > > > > Remove the simple all-or-nothing map cache for ehache. > > > >> Switch to EHCache for Locationmap Cache > >> --------------------------------------- > >> > >> Key: FOR-1031 > >> URL: https://issues.apache.org/jira/browse/FOR-1031 > >> Project: Forrest > >> Issue Type: Improvement > >> Components: Locationmap > >> Reporter: Tim Williams > >> Attachments: lm_cache.diff > >> > >> > >> Should be an easy switch and get much better cache support/configuration > >> options. Expiry of cache can be per-element vs. the current > >> implementation where it expires in its entirey. It will make the LM stuff > >> much cleaner too. > > > > -- > > This message is automatically generated by JIRA. > > - > > You can reply to this email to add a comment to the issue online. > > > > >
