JPPF 4.0 raises the bar in the grid computing arena

Sky-Tiger

VIEW CACHING
The view cache setting is enabled by default in the production environment and pre- vents subsequent render() calls from performing disk I/O. The contents of the tem- plates are saved in memory, greatly improving performance. The side effect of enabling this setting is that you can no longer edit the template files without restarting the server, which is why it’s disabled in development. If you’re running a staging envi- ronment, you’ll likely want to enable this option.
As illustrated in figure 8.12, when view cache is disabled, the template is read from disk on every request. This is what allows you to make changes to a template without restarting the application. When view cache is enabled, the disk is only hit once per template.

Sky-Tiger

View lookup
Now that you know how to configure the view system, let’s take a look at how Express looks up the view, which is where the target view file is located. Don’t worry about cre- ating these templates yet; you’ll do that later.
The process of looking up a view is similar to how Node’s require() works. When res.render() or app.render() is invoked, Express will first check whether a file exists at an absolute path. Next, Express will look relative to the views directory setting dis- cussed in section 8.3.1. Finally, Express will try an index file.