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
This system uses Indiana University's Adobe Media Server instance.
Northwestern University Production System
Northwestern's Avalon System uses 4 machines (3 VM and 1 hardware):
- Avalon web application (VM):
- CPU: Xeon E5-2640 @ 2.50GHz, 2 cores, 4 threads
- RAM: 8GB
- Disk Space: 25GB local storage plus NFS storage
- Fedora, MySQL and the Solr indexer (VM):
- Transcoding (Matterhorn) (Physical box):
- CPU: Xeon E5-2690 v2 @ 3.00GHz 20 cores, 40 threads
- RAM: 128GB
- Disk Space: 4TB local storage plus NFS storage
- Adobe Media Server: External campus enterprise streaming server
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
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.
CPU: 1 Virtual CPU
Disk Space: 500GB (virtual, auto-expanding)