...
There are also other ways to address performance that could be argued are more effective in the long run
- As
As mentioned above, improved server, Apache, Tomcat, and database configuration and tuning - If
(not part of the 1.6 release – more requirements needed) If we can identify key areas where some form of intermediate results are being repeatedly requested from the database, implementing Memcached could be another strategy. However, it may be more effective to provide MySQL more memory since it can use its own strategies for query caching - Tim
Tim Worrall has been looking at our page templates for instances where we could avoid issuing SPARQL queries for the same data repeatedly in the course of generating a single page, and has also been optimizing SPARQL queries that come to his attention - There (not part of the 1.6 release – independent investigation) There is also some indication that bugs in Jena's SDB implementation that make queries other than to a single graph or the union of all graphs much less efficient, at least for MySQL. This is hard to verify, and we have mostly been approaching this by exploring the use of other triple stores via the RDF API added with the VIVO 1.5x releases.
...
- Brian Caruso has proposed adding a unit test for Solr that would build an index from a standard set of VIVO RDF, start Solr, and run standard searches. This would help prevent breaking existing functionality when addressing issues that have come up such as support for diacritics, stop words, and capital letters in the middle of names
- A unit test has been developed for another related project at Cornell and we hope to be able to port this to VIVO, but perhaps not for 1.6
Jira server DuraSpace JIRA key VIVO-102
- Developing repeatable tests of loading one or more large datasets into VIVO. The challenge here is that performance is highly installation dependent. The most urgent problem at Cornell has been the intermittent loss of communication between the VIVO web server and the VIVO database server, which results in some threads of activity simply hanging and never returning. As with many errors that are hard to reproduce, we have developed workarounds that divide large jobs into chunks of data that experience has shown can be removed or added without causing hiccups. Stay tuned.
| Anchor | ||||
|---|---|---|---|---|
|
- Make the About page and Home page HTML content editable through admin interface – this relates to display model changes
Jira server DuraSpace JIRA key VIVO-105 - Note that the home page cannot be made editable through the admin interface as it is too complex
- Offering (Largely complete) Offering improved options for content on the home page, including a set of SPARQL queries to highlight research areas, international focus, or most recent publications
Jira server DuraSpace JIRA key VIVO-106
- Offering (Complete) Offering additional individual page template options
- (Complete) Offering the ability to embed SPARQL query results in individual pages on a per-class basis – for example, to show all research areas represented in an academic department
Jira server DuraSpace JIRA key VIVO-107 - Document the screen capture configuration as part of this
- could
- Could
- put the service-specific aspects in a sub-template that gets imported and could be default not attempt to capture and cache images at all
- are free services out there, but they may not be there in 6 months
- Offering the ability to embed SPARQL query results in individual pages on a per-class basis – for example, to show all research areas represented in an academic department
Jira server DuraSpace JIRA key VIVO-108
| Anchor | ||||
|---|---|---|---|---|
|
...