I've been wondering about the purpose of [git] persistent_cache and what the trade-offs are with enabling it. I've looked through the code, but don't have a clear idea yet. I'd like to improve the TracRepositoryAdmin documentation for the [git] peristent_cache option and the cached [repositories] section attribute (#12406).
The tradeoffs for the cached attribute look straightforward to me. There is more overhead in setting up explicit synchronization, but once properly configured a cached repository is always preferred as it will offer better performance. So the tradeoff is time to configure vs performance. Can anyone describe the purpose of persistent_cache and the trade-offs with enabling it? Would it make sense to have persistent_cache as a per-repository attribute, as in #12406? Similarly, should git_fs_encoding be a per-repository attribute? The other [git] options appear they should be global rather than per-repository, but I wonder about those two. - Ryan #12406: https://trac.edgewall.org/ticket/12406 -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/trac-dev. For more options, visit https://groups.google.com/d/optout.
