Constant look up on the filesystem may be wearing down the hardware and slow down the response.
As the (app) filesystem doesn't change after the launch it would be best to create a copy of the combined directory structure - which includes all controllers/views from brisk and its modules.
That way many lookups could be done against the object saved in memory (instead of the filesystem).
This information could be saved under req.site.dir
Constant look up on the filesystem may be wearing down the hardware and slow down the response.
As the (app) filesystem doesn't change after the launch it would be best to create a copy of the combined directory structure - which includes all controllers/views from brisk and its modules.
That way many lookups could be done against the object saved in memory (instead of the filesystem).
This information could be saved under
req.site.dir