You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

VIVO hardware requirements (in progress)

There is no single preferred configuration for VIVO. Your needs will depend on anticipated size of your VIVO and server load.

Server(s)

VIVO may be hosted on one or more physical servers, on virtual servers, or in the cloud.

Dual virtual server example (Cornell)

  • 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)

Java

  • VIVO requires Java 7 (JDK 1.7) starting with version 1.7



 

 

 

 

  • No labels