From 48b4ded3af3ef594fff4d2ad902d2d07ba5acfb7 Mon Sep 17 00:00:00 2001 From: tankchintan Date: Thu, 21 Jul 2011 21:08:14 +0000 Subject: [PATCH] 1. Improvement of text for "refresh cache". Reviewed by Joseph B. --- .../freemarker/visualization/tools.ftl | 29 ++++++++----------- 1 file changed, 12 insertions(+), 17 deletions(-) diff --git a/productMods/templates/freemarker/visualization/tools.ftl b/productMods/templates/freemarker/visualization/tools.ftl index fc2bd313..c57445bb 100644 --- a/productMods/templates/freemarker/visualization/tools.ftl +++ b/productMods/templates/freemarker/visualization/tools.ftl @@ -8,24 +8,19 @@ Refresh Cached Models for Visualization
Why
-Certain class of visualizations like Temporal graph and Map of Science that work on a large scale -attempt to calculate counts of publications (or grants) for all the organizations within an organization. -These queries tend to be both memory intensive and time consuming. In order to provide a good user experience when -these visualizations are served we decided to save the results of these queries to be reused later. +Large-scale visualizations like the Temporal Graph or the Map of Science involve calculating total counts of publications or +of grants for some entity. Since this means checking also through of its all sub-entities, the underlying queries can be both +memory-intensive and time-consuming. For a faster user experience, we wish to save the results of these queries for later re-use.
What
-To this end we have devised a caching solution which will store information about the organization -hierarchy, which publications were published from which organizations etc (among other things) in -semantic way (i.e. we store the rdf model).
- -We're currently caching these models in-memory, which works nicely, for now. Currently the cache is only built -once, on first user request after a server restart, so the visualization will essentially never be updated -until the server is restarted again. It is not being updated real-time or periodically. This means that the data in these -models might be stale depending upon when was it last created. In future releases we will come -up with a solution that stores these models on disk and be updated periodically.
+To this end we have devised a caching solution which will retain information about the hierarchy of organizations-namely, +which publications are attributed to which organizations-by storing the RDF model.
+We're currently caching these models in memory. The cache is built (only once) on the first user request after a server restart. +Because of this, the same model will be served until the next restart. This means that the data in these models may become stale +depending upon when it was last created. This works well enough for now. In future releases we will improve this solution so that +models are stored on disk and periodically updated.
How
-To refresh these models either restart the server or click on "refresh cache" link above. We realize that -in production VIVO instances it is not feasible to restart the server to refresh these models. Hence we -recommend the above link. Administrators can use this link to trigger regeneration of all the existing -models.
\ No newline at end of file +The models are refreshed each time the server restarts. Since this is not generally practical on production instances, +administrators can instead use the “refresh cache” link above to do this without a restart. +
\ No newline at end of file