Hi all,
Thanks for your answers.
I've already stripped down the supported locale list to the only one
needed. We still have two missed hit for each tried locale.
The tapestry.file-check-interval doesn't help either. The
file-check-interval is seems to be used only for existing files.
I guess th
Also on there is the "tapestry.file-check-interval" which specifies how
long Tapestry should wait before rechecking for changes. In production,
I set that to "1y" because the files aren't going to change. However I
don't know if this affects asset loading or not, but I *think* that once
the fir
Hello
i have already encounter this kind of problem, we solved it by using a
decorator to cache asset access with something like, it was for Tapestry
5.0.18 :
public class AssetSourceCacheDecorator implements AssetSource {
private final Map cache =
CollectionFactory.newConcurrentMap();
private
Doesn't limiting the supported locales to just the ones you support help?
http://tapestry.apache.org/tapestry5.0/guide/conf.html
Uli
Am 29.10.2009 19:39 schrieb Christiansen Merel:
Hello out there,
We're running a quite busy website with tapestry 5.0.18 and we're
hitting a performance problem
Hello out there,
We're running a quite busy website with tapestry 5.0.18 and we're
hitting a performance problem with the ClasspathResource class.
We're using classpath asset and none of them is localised. For each
hit on a page using a classpath asset, we end having 2 missed queries
on the Class
