Under Construction
There are no hard and fast system requirements for running Avalon, but you will want to choose your system depending on your collection size, expected usage, and desired responsiveness. Below are examples of systems running Avalon and simple statistics highlighting their throughput.
Avalon Demo Server http://pawpaw.dlib.indiana.edu/
CPU: 4 cores
RAM: 16 GB RAM
Disk Space: 500 GB Disk
Encoding Time:
This system uses Indiana University's Adobe Media Server instance.
Northwestern University Pilot System
Northwestern's Pilot uses 4 virtual machines:
- Avalon web application: 4GB RAM, 2 CPU
- Fedora, MySQL and the Solr indexer: 4GB RAM, 2 CPU
- Matterhorn: 4GB RAM, 8 CPU
- Adobe Media Server: 4GB RAM, 2 CPU
Encoding Time:
File Formats and Codecs Tested in NU Pilot System*:
- Formats: MPEG-4, FLV, AVI, MOV, OGG, 3GP, RM
- Codecs: avc, aac, pcm, on2 vp6, mp3, xvid, dv, theora, vorbis, h263, amr_nb, rv40, cook
* FFmpeg Supported Source Formats and Codecs
Indiana University Pilot System
- Avalon application (a VM: 4-core, 16 GB memory, 1TB disk, mostly unused ) http://avalon-pilot.dlib.indiana.edu
- Transcoding machine (IBM 3650 model 3 hardware: 12 hyperthreaded cores (looks like 24); 120GB memory 8TB disk, with <1TB currently allocated to Avalon) - this is a three-year-old machine. Replacement plans are in the works.
- This system uses Indiana University's Adobe Media Server instance.
Distributed OVA
CPU: 1 Virtual CPU
RAM: 3GB
Disk Space: 500GB (virtual, auto-expanding)