Page tree
Skip to end of metadata
Go to start of metadata

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

CPU:  4 cores


Disk Space: 500 GB Disk

Encoding Time: 

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

  1. Avalon web application (VM):  
    • CPU: Xeon E5-2640 @ 2.50GHz, 2 cores, 4 threads
    • RAM:  8GB
    • Disk Space: 25GB local storage plus NFS storage
  2. Fedora, MySQL and the Solr indexer (VM):  
  3. 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
  4. 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

* FFmpeg Supported Source Formats and Codecs

Indiana University Production System 

  1. Avalon web application, Fedora, Solr:  
    1. CPU: Intel(R) Xeon(R) CPU E5-2690 v2 @ 3.00GHz
    2. RAM:  24GB
    3. Disk Space: 40GB local storage plus 250GB NFS storage
  2. MySQL:  External service
  3. Transcoding (Matterhorn) (physical box):  
    1. CPU: Intel(R) Xeon(R) CPU E5-2697 v2 @ 2.70GHz, 12 cores, 24 threads
    2. RAM: 128GB
    3. Disk Space: 12TB
  4. Adobe Media Server:  External campus enterprise streaming server

Distributed OVA

CPU: 1 Virtual CPU


Disk Space: 500GB (virtual, auto-expanding)






  • No labels