VIVO hardware requirements (in progress)
There is no single preferred configuration for VIVO. Your needs will depend on anticipated size of your VIVO database and server load.
Server(s)
VIVO may be hosted on one or more physical servers, on virtual servers, or in the cloud. The three currently separable components are the main web application, the MySQL database (with the default Jena SDB triple store), and the Apache Solr search index. Further modularity has been proposed for both reasons of performance and to allow swapping out additional functions such as reasoning or image processing. For reference see the notes from the January
| Site | physical/virtual/cloud | app/solr/db/other | CPU cores/GHz/cache | memory (dedicated vs. burst) | OS | disk storage/MySQL DB size/triple count | average page hits per day/month | notes (e.g., ingest solution, whether allow editing, whether using HTTP caching) |
|---|---|---|---|---|---|---|---|---|
| Cornell | virtual (local) | VIVO, HTTPD, Tomcat, Solr | 2 / 2.67 / 12MB | 16 GB | 64b RHEL | < 150 GB disk | About 12,000 faculty/academics/staff; does allow editing but most done by VIVO staff & students | |
| Cornell | virtual (local) | MySQL | 2 | 2.67 | 12 MB | 8 GB | 64b RHEL | < 150 GB |
MySQL
- MySQL 14.12 distribution 5.0.95 – very likely the RHEL standard distribution
- Database size – the largest reported in the 2014 VIVO Annual Survey (response data) was ~5 GB (10+ million rows in the quads table)
Tomcat
- version: 7
- sample server.xml
- setting memory parameters
- other Java Servlet containers in use
- Glassfish (1 reported)
Java
- VIVO requires Java 7 (JDK 1.7) starting with version 1.7
2014 Survey
The following chart and environment summary shows the range of reported hardware types, memory, and related technologies used.
