...
VIVO may be hosted on one or more physical servers, on virtual servers, or in the cloud.
Dual virtual server example (Cornell)
| Site | physical/virtual/cloud | app/db/both | cores | GHz | cache | memory | OS | storage |
|---|---|---|---|---|---|---|---|---|
| Cornell | virtual (local) | VIVO, HTTPD, Tomcat | 2 | 2.67 | 12 MB | 16GB | 64b RHEL | < 150 GB |
| 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
- vivoprod01: HTTPD and Tomcat, 16G of RAM, 2 cores with 2.67 GHz and 12Mb of cache; 64b Red Hat Enterprise Linux
- vivoprod02: MySQL, 8G of RAM, 2 cores with 2.67 GHz and 12Mb of cache; 64b Red Hat Enterprise Linux
- Both servers need only the minimum level of storage provided for virtual server configurations at Cornell (150 Gb)
- The largest database reported in the 2014 Annual Survey was ~5 GB (10+ million rows in the SDB quads table in MySQL)
MySQL
- MySQL 14.12 distribution 5.0.95 – very likely the RHEL standard distribution
Tomcat
- version: 7
- sample server.xml
- setting memory parameters
- other Java Servlet containers in use
- Glassfish (1 reported)
...