VIVO Documentation
Page History
As a VIVO implementation grows in size and tracks more and more scholarly activity, profile pages can be pulling in hundreds of relationships to render the page, which results in more data being retrieved from the underlying triple store and longer page load times. For example, a profile page for a faculty member with hundreds of publications, which isn't uncommon, can lead to multiple second page loads.
Instead
...
of
...
querying
...
the
...
database
...
each
...
time
...
a
...
page
...
is
...
loaded,
...
a
...
cached
...
version
...
of
...
the
...
page
...
can
...
be
...
served,
...
provided
...
the
...
user
...
is
...
logged
...
out.
...
Since
...
version
...
1.6,
...
VIVO
...
supports
...
HTTP
...
caching
...
directly.
...
To
...
enable,
...
uncomment
...
the
...
"http.createCacheHeaders
...
=
...
true
...
" line
...
in
...
runtime.properties:
| Code Block | ||
|---|---|---|
| ||
# Tell VIVO to generate HTTP headers on its responses to facilitate caching the # profile pages that it creates. # # For more information, see this wiki page: # https://wiki.duraspace.org/display/VIVO/Use+HTTP+caching+to+improve+performance # # Developers will likely want to leave caching disabled, since a change to a # Freemarker template or to a Java class would not cause the page to be # considered stale. # http.createCacheHeaders = true |
...
Overview
Content Tools