Quoting Tommy Davis <list-tmpl@...>:
> We use HTML::Template heavily in conjunction with mod_perl on linux.
> We're considering moving all our templates to a nfs-server. However I'm
> a little concerned about performance.
> H:T does a mtime check everytime we use a template (using "file_cache").
> We could use the "blind_cache" option to avoid that, but it's very
> convenient to be able to update the templates without restarting the
> server ( even on production servers ).
> We've considered adding a "touchfile" option to H:T, like in Apache::Reload.
> Does anyone on the list have experience storing templates on a nfsserver?
If the performance of NFS is worrying you, then why use it? Perhaps an
alternate solution would be just as flexible and not have the performance hit of
I would consider using a central Template repository and syncing it with your
app servers using rsync. Everytime you make a change to a template, you run a
script that rsync's all the templates to your app servers.
This way files are all stored locally on each app server, and file stamps are
only changed when the template is changed.
It does require one extra step to activate your changes, but that is not really
a bad thing in my opinion when dealing with production servers (and using a
touchfile would require an extra step as well).