Rendered markdown should be cached
martinmo opened this issue · 0 comments
martinmo commented
At the moment, each time a task is viewed, the markdown task content is rendered. This includes getting the version
cache busting tag from the repository, which also calls git
under the hood. During normal operation, this is not a problem and I didn't optimize this. However, in the e-exam situation with many more parallel requests than usual, it would make sense to cache the result.